registry / webpackbootstrap5 / 0.0.0-stage
webpackbootstrap5@0.0.0-stage
Temporary package placeholder for staged publishing
AI Security Review
scanned 10d ago · by lpm-firewall-aiSource inspection found only a placeholder manifest and README, with no lifecycle hooks, entrypoints, or executable source. No malicious behavior was identified.
Static reason
No blocking static signals were detected.
Trigger
None identified.
Impact
No package-driven impact was identified.
Mechanism
No executable package behavior is declared or present in the inspected files.
AI rationale
Source inspection found only a placeholder manifest and README, with no lifecycle hooks, entrypoints, or executable source. No malicious behavior was identified.
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 release as a stub placeholder and contains no lifecycle scripts or runtime entrypoints.
- The package contains only package.json and README.md; no executable source files are present.
Evidence against
Behavioral surface
NoLicense
Source & flagged code
1 flagged · loading sourcepackage.jsonView file
1{
"name": "webpackbootstrap5",
"version": "0.0.0-stage",
"stub": true,
"description": "Temporary package placeholder for staged publishing"
}
Low
Suspicious Lifecycle Evidence
package.json identifies this release as a stub placeholder and contains no lifecycle scripts or runtime entrypoints.
package.jsonView on unpkg · L1Findings
2 Low
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to webpackbootstrap5@0.0.0-stage.
See all versions of webpackbootstrap5 for other recorded verdicts.
- Review the evidence and your use of webpackbootstrap5@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.