registry / corporate-front-vue / 0.0.1-security
corporate-front-vue@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-aiStatic inspection found no executable files, lifecycle hooks, entrypoints, dependencies, network access, or file mutation. The README describes historical removal of malicious code, but this placeholder version itself contains no attack behavior.
Static reason
No blocking static signals were detected.
Trigger
None
Impact
None observed
Mechanism
No executable behavior
AI rationale
Static inspection found no executable files, lifecycle hooks, entrypoints, dependencies, network access, or file mutation. The README describes historical removal of malicious code, but this placeholder version itself contains no attack behavior.
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 placeholder for a previously removed package.
Evidence against
- package.json has no scripts, dependencies, bin, or runtime entrypoints.
- Package inventory contains only package.json and README.md.
- README.md is documentation only; no executable payload or install/import behavior exists.
Behavioral surface
NoLicense
Source & flagged code
0 flaggedNo flagged code excerpts are attached to this scan.
Findings
2 Low
LowNo License
LowAi Review Evidence
Affected versions and remediation
This report applies to corporate-front-vue@0.0.1-security.
See all versions of corporate-front-vue for other recorded verdicts.
- Review the evidence and your use of corporate-front-vue@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.