Trusted — Risk Score 5/100
Last scan:19 hr ago Rescan
5 /100
mindflow
Converts text, Markdown files, or Txt files into mind map images using markmap and puppeteer
The 'mindflow' skill is a legitimate text-to-mindmap converter that uses markmap and puppeteer. The JavaScript implementation is straightforward and matches its documented purpose.
Skill Namemindflow
Duration27.3s
Enginepi
Safe to install
No action needed. The skill is safe to use.

Findings 2 items

Severity Finding Location
Low
Dependencies not version-pinned Supply Chain
SKILL.md shows 'npm install markmap-cli markmap-lib markmap-render puppeteer' without version constraints, which could allow malicious updates
npm install markmap-cli markmap-lib markmap-render puppeteer
→ Use pinned versions: npm install [email protected] [email protected] [email protected]
SKILL.md:13
Info
Puppeteer sandbox flags Priv Escalation
Puppeteer launches with --no-sandbox and --disable-setuid-sandbox flags, common in containerized environments
args: ['--no-sandbox', '--disable-setuid-sandbox']
→ This is standard practice; not a security concern in this context
scripts/html-to-image.js:287
ResourceDeclaredInferredStatusEvidence
Filesystem READ READ ✓ Aligned Line 302: fs.readFileSync(options.input, 'utf-8')
Filesystem WRITE WRITE ✓ Aligned Line 331: screenshotOptions.path = outputPath
Network NONE NONE No outbound network calls; puppeteer internal browser networking only
Shell NONE NONE No subprocess/exec calls found

File Tree

2 files · 17.3 KB · 574 lines
JavaScript 1f · 456L Markdown 1f · 118L
├─ 📁 scripts
│ └─ 📜 html-to-image.js JavaScript 456L · 13.4 KB
└─ 📝 SKILL.md Markdown 118L · 3.9 KB

Dependencies 4 items

PackageVersionSourceKnown VulnsNotes
puppeteer * npm No Version not pinned in documentation
markmap-cli * npm No Version not pinned in documentation
markmap-lib * npm No Version not pinned in documentation
markmap-render * npm No Version not pinned in documentation

Security Positives

✓ Code is clean, well-structured, and readable
✓ No obfuscation, base64 encoding, or eval() usage
✓ No credential harvesting or sensitive data access
✓ No network exfiltration or C2 communication
✓ No hidden functionality - implementation matches documentation
✓ Input validation present for file existence and type
✓ Error handling with try/finally blocks
✓ No reverse shell or RCE capabilities