registry / data-pipeline-testmetest / 0.0.0-stage
data-pipeline-testmetest@0.0.0-stage
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest contains no lifecycle scripts, runtime entrypoints, or dependencies, and the package file listing contains no runtime source files. The inspected source supports a clean verdict.
Static reason
No blocking static signals were detected.
Trigger
No package execution trigger is declared in package.json.
Impact
No harmful effect was identified in the inspected source.
Mechanism
The inspected manifest contains package metadata only.
AI rationale
The manifest contains no lifecycle scripts, runtime entrypoints, or dependencies, and the package file listing contains no runtime source files. The inspected source supports a clean verdict.
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 contains only package identity, a stub marker, and a placeholder description; it defines no scripts, entrypoints, or dependencies.
Evidence against
Behavioral surface
NoLicense
Source & flagged code
1 flagged · loading sourcepackage.jsonView file
1{
"name": "data-pipeline-testmetest",
"version": "0.0.0-stage",
"stub": true,
"description": "Temporary package placeholder for staged publishing"
}
Low
Suspicious Dependency Evidence
package.json contains only package identity, a stub marker, and a placeholder description; it defines no scripts, entrypoints, or dependencies.
package.jsonView on unpkg · L1Findings
2 Low
LowNo License
LowSuspicious Dependency Evidencepackage.json
Affected versions and remediation
This report applies to data-pipeline-testmetest@0.0.0-stage.
See all versions of data-pipeline-testmetest for other recorded verdicts.
- Review the evidence and your use of data-pipeline-testmetest@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.