registry / atlas-project-harness / 0.1.0-beta.19
atlas-project-harness@0.1.0-beta.19
践行 Project Harness 的全流程 AI 编程工作流治理引擎
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe manifest has no install hook, and the inspected extension behavior aligns with the package’s project harness features. The outbound report path uses GitHub authentication to submit issue fields to the package’s GitHub repository; no concrete attack behavior was established.
Static reason
No blocking static signals were detected.
Trigger
Setup requires `/atlas init`; reporting is exposed as a package feature for design issues.
Impact
No unauthorized mutation, credential harvesting, or unrelated data collection was established.
Mechanism
The extension checks the local project after qualifying turns. The report helper posts supplied issue fields to GitHub using GitHub authentication.
AI rationale
The manifest has no install hook, and the inspected extension behavior aligns with the package’s project harness features. The outbound report path uses GitHub authentication to submit issue fields to the package’s GitHub repository; no concrete attack behavior was established.
Network endpoints1
api.github.com/repos/{repo}/issues
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI and agent extension, with no install lifecycle hook.
- Project setup runs through the explicit `/atlas init` command.
- The extension’s automatic turn-end check requires a completed turn with tool results and runs a local project check.
- The required test file contains Python parser fixtures and assertions, not an executable payload.
- The report helper sends supplied report fields to GitHub’s API using GitHub authentication; this matches the package’s reporting feature.
Evidence against
- The extension can direct an agent to submit a design issue, and the report helper defaults to the package’s GitHub repository; this is an outbound transfer, but the source scopes it to design reporting and shows no harvesting behavior.
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.19.
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.19 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.