registry / eslint-config-compact-base / 0.0.0-stage
eslint-config-compact-base@0.0.0-stage
Temporary package placeholder for staged publishing
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe inspected manifest identifies a placeholder stub and declares no install-time or runtime behavior. No concrete attack surface was found.
Static reason
No blocking static signals were detected.
Trigger
No lifecycle hook or executable entrypoint is declared.
Impact
No harmful behavior is established by the inspected source.
Mechanism
The manifest only identifies the package, its version, and its stub status.
AI rationale
The inspected manifest identifies a placeholder stub and declares no install-time or runtime behavior. No concrete attack surface was found.
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json marks the package as a stub and declares no lifecycle hooks, executable entrypoints, dependencies, or runtime exports.
Evidence against
Behavioral surface
NoLicense
Source & flagged code
1 flagged · loading sourcepackage.jsonView file
1{
"name": "eslint-config-compact-base",
"version": "0.0.0-stage",
"stub": true,
"description": "Temporary package placeholder for staged publishing"
}
Low
Suspicious Lifecycle Evidence
package.json marks the package as a stub and declares no lifecycle hooks, executable entrypoints, dependencies, or runtime exports.
package.jsonView on unpkg · L1Findings
2 Low
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to eslint-config-compact-base@0.0.0-stage.
See all versions of eslint-config-compact-base for other recorded verdicts.
- Review the evidence and your use of eslint-config-compact-base@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.