AI Security Review
scanned 3h ago · by lpm-firewall-aiNo executable install-time or runtime attack surface is established. The package consists of metadata plus an empty index file; opaque keywords are inert metadata.
Static reason
No blocking static signals were detected.
Trigger
None; package installation does not declare lifecycle scripts or an executable entrypoint.
Impact
No source-backed execution, exfiltration, persistence, or file mutation path exists.
Mechanism
Inert oversized metadata payload
Rationale
Direct inspection found no code path capable of executing the opaque metadata or performing harmful actions. The unusual keyword payload is inert and does not justify a blocking or warning verdict without a reachable mechanism.
Evidence
package.jsonindex.js
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for block
- package.json contains 274 opaque high-entropy keyword strings totaling 68,268 characters.
- index.js exists but is empty; the package exposes no executable source.
Evidence against
- package.json has only name, version, license, description, and keywords.
- No scripts, bin, main, module, browser, dependencies, or optionalDependencies are declared.
- No install lifecycle hook or runtime entrypoint exists.
- No network, filesystem, shell, dynamic execution, or credential-access code was found in package files.
Behavioral surface
Trivial
Source & flagged code
1 flagged · loading sourcepackage.jsonView file
•Published source reference
Low
Ai Review Evidence
package.json contains 274 opaque high-entropy keyword strings totaling 68,268 characters.
package.jsonView on unpkgFindings
2 Low
LowAi Review Evidencepackage.json
LowAi Review Evidence