monogrok@0.0.1-security
security holding package
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe inspected package contains only a manifest and explanatory README, with no executable or lifecycle behavior. The README's historical claim does not establish malicious behavior in version `0.0.1-security`.
Static reason
No blocking static signals were detected.
Trigger
None
Impact
None established
Mechanism
No executable package behavior
AI rationale
The inspected package contains only a manifest and explanatory README, with no executable or lifecycle behavior. The README's historical claim does not establish malicious behavior in version `0.0.1-security`.
Evidence
package.jsonREADME.md
Decision evidence
public snapshotAI called this Clean at 98.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- `README.md` describes this as a security holding placeholder and references prior removed code.
Evidence against
- `package.json` has no scripts, dependencies, bin, or runtime entrypoints.
- Package inventory contains only `package.json` and `README.md`.
- No executable source, install hook, network logic, or file/credential access exists in inspected files.
Behavioral surface
NoLicense
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
2 Low
LowNo License
LowAi Review Evidence
Affected versions and remediation
This report applies to monogrok@0.0.1-security.
See all versions of monogrok for other recorded verdicts.
- Review the evidence and your use of monogrok@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.