registry / ts-biginteger-lib / 0.0.1-security
ts-biginteger-lib@0.0.1-security
security holding package
AI Security Review
scanned 3mo ago · by lpm-firewall-aiDirect inspection found no executable source, lifecycle hook, entrypoint, dependency, or network behavior. The README's claim about previously removed code does not establish malicious behavior in this published placeholder version.
Static reason
No blocking static signals were detected.
Trigger
None
Impact
No package-originated runtime, install-time, network, or filesystem action
Mechanism
No executable behavior present
AI rationale
Direct inspection found no executable source, lifecycle hook, entrypoint, dependency, or network behavior. The README's claim about previously removed code does not establish malicious behavior in this published placeholder version.
Evidence
package.jsonREADME.md
Decision evidence
public snapshotAI called this Clean at 99.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- README.md states this is a security holding package for previously removed malicious code.
Evidence against
- package.json contains only name, version, description, and repository metadata.
- package.json has no lifecycle scripts or executable entrypoints.
- Package contains only package.json and README.md.
- No install-time, import-time, network, shell, file-write, credential, or payload code exists.
Behavioral surface
NoLicense
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
2 Low
LowNo License
LowAi Review Evidence
Affected versions and remediation
This report applies to ts-biginteger-lib@0.0.1-security.
See all versions of ts-biginteger-lib for other recorded verdicts.
- Review the evidence and your use of ts-biginteger-lib@0.0.1-security 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.