Pre-open repo agent-surface audit
By TextForAgents LLC. Before your agent opens a repository received as files (zip, shared drive, archive attached to a bug report), run this gate — before the agent's first git call. It never executes the tree.
It enumerates the complete agent-control surface on two separately graded surfaces:
- EXECUTION — git-config command sinks (
core.fsmonitor,hooksPath,sshCommand, filter/diff drivers), hooks and every hooksPath target,.gitattributesdrivers,.gitmodulesext:: URLs, MCP server commands, npm lifecycle scripts — at any depth and through symlinks. - EXAMINATION — model pins against your pinned policy, review-scope exclusions (including implicit "only review X" omissions), do-not-reaudit clauses, permission widenings, unbounded agent-binding prose.
It issues a per-harness × per-version verdict — OPEN /
OPEN-QUARANTINED / DO-NOT-OPEN — from a maintained patch-status matrix
(matrix version 2026-10-28.1), and a receipt core whose tree hash binds
file contents. The sanitise command emits a quarantined copy accepted
only when it re-audits with zero high findings.
Stated plainly: a verdict grades the enumerated agent-control surface only — it is not a general malware, vulnerability, or safety determination about the tree's code. Enumeration is complete on the proven classes, but prose classification is pattern-based: a genuinely novel paraphrase can escape classification while never escaping enumeration. Verdicts are matrix-versioned. Willingness to pay is unmeasured.
Quickstart
pip install repo-agent-surface-pre-open-audit
cat > policy.json <<'EOF'
{"min_model_tier": 3, "forbidden_scope_exclusions": ["tests/", "tests", "test/"]}
EOF
preopen-audit audit /path/to/received-tree --harness claude-code --version 2.1.252 --policy policy.json
preopen-audit sanitise /path/to/received-tree /path/to/quarantined-copy
Python 3 standard library only. The local CLI processes trees on your own machine — no tree content leaves it. Hosted API/MCP form with signed receipts: https://textforagents.com/products/repo-agent-surface-pre-open-audit/ Support: support@textforagents.com
Metadata
Release files for repo-agent-surface-pre-open-audit 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| repo_agent_surface_pre_open_audit-1.0.3.tar.gz | 13.7 kB | Without provenance | Details for repo_agent_surface_pre_open_audit-1.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| repo_agent_surface_pre_open_audit-1.0.3-py3-none-any.whl | Python 3 | none | any | Details for repo_agent_surface_pre_open_audit-1.0.3-py3-none-any.whl |
Total release size: 26.3 kB
Release files / repo_agent_surface_pre_open_audit-1.0.3.tar.gz
| Download URL | repo_agent_surface_pre_open_audit-1.0.3.tar.gz |
|---|---|
| Size | 13.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4783deee5f832d603ae74f499ede0c81ee9e7170866c45f14a4f2f53e3565b3c
|
|
BLAKE2b-256 checksum How to use checksums |
8c5d122fb8478a3ad32ea433d8c9ddd7899cf2fd99decd0c8ee929b1367e017b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / repo_agent_surface_pre_open_audit-1.0.3-py3-none-any.whl
| Download URL | repo_agent_surface_pre_open_audit-1.0.3-py3-none-any.whl |
|---|---|
| Size | 12.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0b9d94cfbfba53f3f09c2229b3736108b41e6bc9853097ee1429befa6865eece
|
|
BLAKE2b-256 checksum How to use checksums |
a3b91b66dc70b3c3faef3b71cbbc9d29afe8ddf214edafc2cba0c7398a8af36a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for repo-agent-surface-pre-open-audit 1.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.