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