registry / kiyoramarkets / 0.0.0-stage
kiyoramarkets@0.0.0-stage
Temporary package placeholder for staged publishing
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe manifest contains only package metadata and a stub description, with no lifecycle scripts or executable entrypoints. The package snapshot provides no source evidence of malicious behavior.
Static reason
No blocking static signals were detected.
Trigger
No lifecycle hook or executable entrypoint is defined.
Impact
No attack impact was identified.
Mechanism
The manifest identifies the package as a stub placeholder and declares no executable behavior.
AI rationale
The manifest contains only package metadata and a stub description, with no lifecycle scripts or executable entrypoints. The package snapshot provides no source evidence of malicious behavior.
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 identifies this as a stub placeholder and defines no lifecycle scripts or executable entrypoints.
Evidence against
Behavioral surface
NoLicense
Source & flagged code
1 flagged · loading sourcepackage.jsonView file
1{
"name": "kiyoramarkets",
"version": "0.0.0-stage",
"stub": true,
"description": "Temporary package placeholder for staged publishing"
}
Low
Suspicious Lifecycle Evidence
package.json identifies this as a stub placeholder and defines no lifecycle scripts or executable entrypoints.
package.jsonView on unpkg · L1Findings
2 Low
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to kiyoramarkets@0.0.0-stage.
See all versions of kiyoramarkets for other recorded verdicts.
- Review the evidence and your use of kiyoramarkets@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.