registry / babel-polyfill-plugin-corejs2 / 0.0.0-stage
babel-polyfill-plugin-corejs2@0.0.0-stage
Temporary package placeholder for staged publishing
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe inspected manifest marks this package as a stub placeholder and declares no lifecycle scripts or runtime entrypoints. No attack behavior was identified.
Static reason
No blocking static signals were detected.
Trigger
No package execution trigger is declared in the manifest.
Impact
No package-driven impact was identified.
Mechanism
No executable behavior is declared in the inspected package manifest.
AI rationale
The inspected manifest marks this package as a stub placeholder and declares no lifecycle scripts or runtime entrypoints. No attack 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
- The manifest identifies the package as a temporary placeholder and marks it as a stub; it defines no lifecycle scripts or runtime entrypoints.
Evidence against
Behavioral surface
NoLicense
Source & flagged code
1 flagged · loading sourcepackage.jsonView file
1{
"name": "babel-polyfill-plugin-corejs2",
"version": "0.0.0-stage",
"stub": true,
"description": "Temporary package placeholder for staged publishing"
}
Low
Suspicious Lifecycle Evidence
The manifest identifies the package as a temporary placeholder and marks it as a stub; it defines 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 babel-polyfill-plugin-corejs2@0.0.0-stage.
See all versions of babel-polyfill-plugin-corejs2 for other recorded verdicts.
- Review the evidence and your use of babel-polyfill-plugin-corejs2@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.