registry / localization-lib / 0.0.1-security
localization-lib@0.0.1-security
security holding package
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiDirect inspection found no lifecycle hooks, source entrypoints, or executable payload. The README's historical claim is not source evidence of malicious behavior in this published package version.
Static reason
No blocking static signals were detected.
Trigger
None
Impact
No package-originated runtime or install-time effect
Mechanism
No executable behavior
AI rationale
Direct inspection found no lifecycle hooks, source entrypoints, or executable payload. The README's historical claim is not source evidence of malicious behavior in this published package 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
Evidence against
- `package.json` contains only package metadata; no scripts or entrypoints.
- Package inventory contains only `package.json` and `README.md`.
- `README.md` is a holding-package notice and contains no executable code.
- No network, credential, filesystem, shell, dynamic-code, or agent-control logic exists in inspected files.
Behavioral surface
NoLicense
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 Low
LowNo License
Affected versions and remediation
This report applies to localization-lib@0.0.1-security.
See all versions of localization-lib for other recorded verdicts.
- Review the evidence and your use of localization-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.