registry / @worrisome/reutil / 0.0.0-stage
@worrisome/reutil@0.0.0-stage
Temporary package placeholder for staged publishing
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe manifest contains only package identity, stub status, and a placeholder description; the package has no implementation source. No concrete malicious behavior was found.
Static reason
No blocking static signals were detected.
Trigger
No package execution trigger is declared in the manifest.
Impact
No attack impact was identified.
Mechanism
No implementation behavior is present in the package files.
AI rationale
The manifest contains only package identity, stub status, and a placeholder description; the package has no implementation source. No concrete malicious behavior was found.
Evidence
package.json
Decision evidence
public snapshotAI called this Clean at 98.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json identifies this as a stub placeholder and contains no lifecycle scripts or runtime entrypoints; the package contains no implementation source.
Evidence against
Behavioral surface
NoLicense
Source & flagged code
1 flagged · loading sourcepackage.jsonView file
1{
"name": "@worrisome/reutil",
"version": "0.0.0-stage",
"stub": true,
"description": "Temporary package placeholder for staged publishing"
}
Low
Suspicious Lifecycle Evidence
package.json identifies this as a stub placeholder and contains no lifecycle scripts or runtime entrypoints; the package contains no implementation source.
package.jsonView on unpkg · L1Findings
2 Low
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @worrisome/reutil@0.0.0-stage.
See all versions of @worrisome/reutil for other recorded verdicts.
- Review the evidence and your use of @worrisome/reutil@0.0.0-stage 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.