@eldestar/curator
A portable session-protocol skill for Claude Code — instant orientation, no doc sprawl.
This report shows the evidence for @eldestar/curator@1.1.0. 2 of 2 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiThe package's core behavior is an install-time rewrite of Claude Code's global hooks/settings, which matches the blockable AI-agent control-hijack policy even though no classic malware or network exfiltration was found. The absence of network and secret harvesting reduces traditional malware indicators but does not neutralize the unconsented lifecycle control-surface mutation.
Decision evidence
public snapshot- package.json runs postinstall: node scripts/postinstall.js
- scripts/postinstall.js writes package files into ~/.claude/commands and ~/.claude/curator-*.sh/js
- scripts/postinstall.js rewrites ~/.claude/settings.json hooks.SessionStart to execute ~/.claude/curator-hook.sh
- scripts/postinstall.js also wires hooks.Stop when --enforce is passed
- hooks/session-start.sh injects .protocol.md, git state, and project docs into Claude session context
- No network clients or exfiltration endpoints found
- No eval/vm/Function or dynamic remote code loading found
- Hook exits unless .protocol.md exists in the active project
- Session log path has checks against absolute paths, traversal, and symlink escape
Source & flagged code
3 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage ships non-JavaScript build or shell helper files.
hooks/session-start.shView on unpkgFindings
Affected versions and remediation
This report applies to @eldestar/curator@1.1.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @eldestar/curator@1.1.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.