registry / atlas-project-harness / 0.1.0-beta.18
atlas-project-harness@0.1.0-beta.18
践行 Project Harness 的全流程 AI 编程工作流治理引擎
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and its runtime behavior is aligned with project workflow management. The flagged test file contains parser tests; GitHub reporting is a distinct command using GitHub authentication with the GitHub API.
Static reason
No blocking static signals were detected.
Trigger
The extension runs in the Pi host; issue submission requires running `atlas report` with report details.
Impact
No unauthorized credential disclosure, account action, persistence, or hidden install-time mutation was established.
Mechanism
The extension checks Atlas project state and workflow gates. The report command submits issue details to GitHub using GitHub authentication.
AI rationale
The package has no install lifecycle hook, and its runtime behavior is aligned with project workflow management. The flagged test file contains parser tests; GitHub reporting is a distinct command using GitHub authentication with the GitHub API.
Network endpoints1
api.github.com
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI and extension, with only test and documentation scripts and no install lifecycle hook.
- The flagged test file contains parser fixtures and golden assertions.
- The extension registers an Atlas command; its runtime hooks check the current project and run workflow checks after tool activity.
- GitHub issue posting is available through the separate report command and requires report fields; it uses GitHub authentication with the GitHub API.
- The report destination is GitHub's API, and the supplied issue content is sent as an issue payload.
Evidence against
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flagged · loading sourcebin/atlas.jsView file
1#!/usr/bin/env node
L2: const { spawnSync } = require('child_process');
L3: const path = require('path');
Medium
Dynamic Require
Package source references dynamic require/import behavior.
bin/atlas.jsView on unpkg · L1patches/workflow-skill-routing/apply-patches.pyView file
•path = patches/workflow-skill-routing/apply-patches.py
kind = build_helper
sizeBytes = 10653
magicHex = [redacted]
Medium
Ships Build Helper
Package ships non-JavaScript build or shell helper files.
patches/workflow-skill-routing/apply-patches.pyView on unpkgtests/test_shared_kernel.pyView file
Findings
2 High5 Medium5 Low
HighPayload In Excluded Dirtests/test_shared_kernel.py
HighSemantic Analysis Limitedextensions/pi.ts#virtual:normalized:round1
MediumDynamic Requirebin/atlas.js
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperpatches/workflow-skill-routing/apply-patches.py
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to atlas-project-harness@0.1.0-beta.18.
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.18 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.