@saidulbadhon/jssm-cli
CLI for JSSM - Simple environment variable manager
This report shows the evidence for @saidulbadhon/jssm-cli@2.0.1. 2 of 3 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection confirms a concrete install-time destructive action via rmSync against broad global/user binary paths. Package-aligned CLI env sync and auth behavior is not itself malicious, but the postinstall deletion behavior warrants blocking.
Decision evidence
public snapshot- package.json defines install-time postinstall: node scripts/postinstall.mjs
- scripts/postinstall.mjs scans PATH and common global manager bins for executable named jssm
- scripts/postinstall.mjs removes candidates with rmSync unless they resolve into this package or ~/.jssm
- install hook can delete /usr/local/bin/jssm, /opt/homebrew/bin/jssm, ~/.bun/bin/jssm, pnpm/yarn global jssm without user consent
- dist/index.cjs also contains CLI-triggered global self-update via npm install -g @saidulbadhon/jssm-cli@latest
- dist/index.cjs network use is mostly package-aligned auth/project/env sync to jssm-api.jutsu.ai
- dist/index.cjs .env upload/pull operations are invoked by explicit CLI commands and prompts
- Auth token storage is under ~/.jssm/auth for the package's own service
- No AI-agent control-surface writes found
- No obfuscated staged payload or arbitrary remote code execution found
Source & flagged code
5 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 unpkgFindings
Affected versions and remediation
This report applies to @saidulbadhon/jssm-cli@2.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @saidulbadhon/jssm-cli@2.0.1. 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.