registry / babel-eslint-parser-legacy / 0.0.1-security
babel-eslint-parser-legacy@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, entrypoints, dependencies, or source files capable of malicious behavior. The holding-package text is inert and does not create an attack surface.
Static reason
No blocking static signals were detected.
Trigger
None
Impact
No package-originated runtime, install-time, or import-time action established.
Mechanism
No executable package behavior
AI rationale
Direct inspection found no lifecycle hooks, entrypoints, dependencies, or source files capable of malicious behavior. The holding-package text is inert and does not create an attack surface.
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 executable entrypoints.
- README.md describes a security holding package and contains no executable instructions.
- Package inventory contains only README.md and package.json.
- No network, shell, dynamic execution, filesystem mutation, or credential access code is present.
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 babel-eslint-parser-legacy@0.0.1-security.
See all versions of babel-eslint-parser-legacy for other recorded verdicts.
- Review the evidence and your use of babel-eslint-parser-legacy@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.