registry / class-synth / 0.0.1-security
class-synth@0.0.1-security
security holding package
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe inspected class-synth@0.0.1-security contents are non-executable and define no install or runtime behavior. README.md describes prior removed malware, but supplies no evidence of malicious behavior in this published holding version.
Static reason
No blocking static signals were detected.
Trigger
None
Impact
None
Mechanism
No executable package behavior
AI rationale
The inspected class-synth@0.0.1-security contents are non-executable and define no install or runtime behavior. README.md describes prior removed malware, but supplies no evidence of malicious behavior in this published holding 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
- README.md states this is an npm security holding package after earlier malicious code was removed.
Evidence against
- package.json contains only name, version, description, and repository metadata.
- package.json defines no lifecycle hooks or executable entrypoints.
- The package contains only package.json and README.md; no JavaScript, binaries, or install scripts are present.
- No network endpoints, file writes, credential access, dynamic execution, or persistence code exists in the inspected files.
Behavioral surface
NoLicense
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
2 Low
LowNo License
LowAi Review Evidence
Affected versions and remediation
This report applies to class-synth@0.0.1-security.
See all versions of class-synth for other recorded verdicts.
- Review the evidence and your use of class-synth@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.