registry / autotel-terminal / 46.0.0
autotel-terminal@46.0.0
⚠ Under reviewTerminal dashboard for autotel traces using react-ink
Static Scan Results
scanned 23d ago · by rust-scannerStatic analysis completed at 93.0% confidence. No malicious behavior was detected; 8 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
EnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
2 flagged · loading sourcedist/cli.cjs#virtual:normalized:round1View file
•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 2
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/cli.cjs#virtual:normalized:round1View on unpkgdist/cli.cjsView file
•matchType = previous_version_dangerous_delta
matchedPackage = autotel-terminal@45.0.0
matchedIdentity = npm:YXV0b3RlbC10ZXJtaW5hbA:45.0.0
similarity = 0.429
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/cli.cjsView on unpkgFindings
2 High2 Medium4 Low
HighSemantic Analysis Limiteddist/cli.cjs#virtual:normalized:round1
HighPrevious Version Dangerous Deltadist/cli.cjs
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to autotel-terminal@46.0.0.
See all versions of autotel-terminal for other recorded verdicts.
- Review the evidence and your use of autotel-terminal@46.0.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.