slaunt@0.1.12
Privacy-first MCP agent access auditor for Claude and Codex
Static Scan Results
scanned 2mo ago · by rust-scannerStatic analysis completed at 93.0% confidence. No malicious behavior was detected; 9 low-signal pattern(s) were surfaced and cleared.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Decision evidence
public snapshotBehavioral surface
CryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
2 flaggeddist/explanation/local.js#virtual:normalized:round1View file
•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 1
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/explanation/local.js#virtual:normalized:round1View on unpkgdist/explanation/local.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = slaunt@0.1.10
matchedIdentity = npm:c2xhdW50:0.1.10
similarity = 0.850
summary = stored previous version shares package body but lacks this dangerous source file
High
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/explanation/local.jsView on unpkgFindings
2 High2 Medium5 Low
HighSemantic Analysis Limiteddist/explanation/local.js#virtual:normalized:round1
HighPrevious Version Dangerous Deltadist/explanation/local.js
MediumNetwork
MediumEnvironment Vars
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to slaunt@0.1.12.
See all versions of slaunt for other recorded verdicts.
- Review the evidence and your use of slaunt@0.1.12 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.