registry / cktool-core / 0.0.1-security
cktool-core@0.0.1-security
security holding package
AI Security Review
scanned 3mo ago · by lpm-firewall-aiDirect inspection found no executable source, install hook, entrypoint, or malicious primitive. The README's historical claim does not establish malicious behavior in this placeholder version.
Static reason
No blocking static signals were detected.
Trigger
None
Impact
None established
Mechanism
No executable package behavior
AI rationale
Direct inspection found no executable source, install hook, entrypoint, or malicious primitive. The README's historical claim does not establish malicious behavior in this placeholder version.
Evidence
package.jsonREADME.md
Decision evidence
public snapshotAI called this Clean at 99.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
Evidence against
- package.json has no lifecycle scripts or code entrypoints.
- Only package files are package.json and README.md.
- README.md describes this as a security holding placeholder; it contains no executable content.
- No network, shell, credential, file-write, or dynamic-execution code found.
Behavioral surface
NoLicense
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 Low
LowNo License
Affected versions and remediation
This report applies to cktool-core@0.0.1-security.
See all versions of cktool-core for other recorded verdicts.
- Review the evidence and your use of cktool-core@0.0.1-security 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.