@ngocsangairvds/vsaf@6.11.0
is it ready to use ?
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is a real, user-invoked AI-agent configuration capability and merits a warning under the firewall policy. It is not concrete malicious behavior because the npm lifecycle hook is package-local and the control-surface writes are command-gated.
Decision evidence
public snapshot- Explicit `vsaf install` deploys hook files and merges Claude settings.
- NTAPP ships event-hook declarations that execute project-local scripts for Claude events.
- Optional Bitbucket integration reads an existing token or Git credential for user-requested repository access.
- The postinstall hook only creates a package-local `node_modules/@vsaf/core` link.
- Agent configuration changes require the explicit `vsaf install` command.
- Global sync is off by default and exposed as `--sync-global`; no stealth persistence or exfiltration was found.
Source & flagged code
21 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 @ngocsangairvds/vsaf@6.11.0.
See all versions of @ngocsangairvds/vsaf for other recorded verdicts.
- Review the evidence and your use of @ngocsangairvds/vsaf@6.11.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.