atlas-loop@0.1.8
CAUTION· install onlyPublisher claims: "Atlas Loop —— 通用的递归学习地图 Agent Skill:把任何陌生主题拆解为独立离线的交互式 HTML 地图,并为每个节点配上深入探究与递归子图提示。" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-14 and scored it 78/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
.replace(/import\.meta\.env/g, '({MODE:"production"})')Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.npx @liduchuan/atlas-loop verify --html <output.html>Fix: Pin versions and sources; vendor anything fetched at install time.npx @liduchuan/atlas-loop install [--dir <skills-dir>]Fix: Pin versions and sources; vendor anything fetched at install time.console.error('用法:node build_atlas.mjs --data <graph-data.json> [--out <output.html>]');Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.node <skill_dir>/scripts/build_atlas.mjs --data /tmp/atlas-loop-<ts>/graph-data.json --out <output_html>Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.return res.outputFiles[0].text.replace(/import\.meta\.env/g, '({MODE:"development"})');Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.npx @liduchuan/atlas-loop dev [--port 5179] [--data <graph-data.json>]Fix: Pin versions and sources; vendor anything fetched at install time.npx @liduchuan/atlas-loop build --data <graph-data.json> [--out <output.html>]Fix: Pin versions and sources; vendor anything fetched at install time.return fs.readFileSync(tmpOut, 'utf8').replace(/import\.meta\.env/g, '({MODE:"development"})');Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.npx @liduchuan/atlas-loop build --data <graph-data.json> [--out <output.html>]Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
No advisories in OSV for @liduchuan/atlas-loop@0.1.8 as of 47 min ago. This is the package itself, not its dependencies.
What would make this Verified
2 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim liduchuan: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.