registry / ng-search-api / 0.0.1-security
ng-search-api@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 shows this version is a minimal placeholder, not code capable of malicious behavior. README.md's statement about a removed historical package is not evidence of malicious behavior in the inspected release.
Static reason
No blocking static signals were detected.
Trigger
None
Impact
No package-originated runtime or install-time action established.
Mechanism
Metadata-only security holding package
AI rationale
Direct inspection shows this version is a minimal placeholder, not code capable of malicious behavior. README.md's statement about a removed historical package is not evidence of malicious behavior in the inspected release.
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, entrypoints, dependencies, or bin fields.
- README.md identifies this release as a security holding placeholder.
- The package contains only README.md and package.json; neither implements executable behavior.
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 ng-search-api@0.0.1-security.
See all versions of ng-search-api for other recorded verdicts.
- Review the evidence and your use of ng-search-api@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.