atlas-project-harness@0.1.0-beta.28
践行 Project Harness 的全流程 AI 编程工作流治理引擎
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and inspected runtime, installer, and report behavior is project-aligned or explicitly invoked. Scanner similarity and payload hints were not confirmed by source inspection.
Decision evidence
public snapshot- package.json has no preinstall, install, or postinstall hook; its scripts are tests and documentation commands.
- The flagged test file contains ordinary kernel alias and loader checks, not an executable payload.
- The extension’s startup hook checks project status and returns without adding behavior when the project is not an Atlas project.
- The CLI runs the installer only for an explicit init command; install.sh also guards overwriting an existing installation.
- Reporting is an explicit CLI command that sends a report to GitHub using GitHub credentials; the inspected code does not show automatic credential disclosure.
Source & flagged code
6 flagged · loading sourceSource file is highly similar to a previously finalized malicious package; route for source-aware review.
bin/atlas.jsView on unpkgSource fingerprint signature matches a known malicious package signature; route for source-aware review.
bin/atlas.jsView on unpkgFindings
Affected versions and remediation
This report applies to atlas-project-harness@0.1.0-beta.28.
See all versions of atlas-project-harness for other recorded verdicts.
- Review the evidence and your use of atlas-project-harness@0.1.0-beta.28 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.