Authorized Artifact Auditor
A CLI toolkit plus AI Agent skills for authorized software auditing — from binary fingerprinting to SBOM, CVE intel and remediation reports.
- Source repo
- ptn1411/skill
- Stars
- ★ 327
- Last updated
- 14d ago
- Primary language
- Python
- FA score
- 41/100 · Major gaps
At a glance
- How it runs
- Works with
- Universal · cross-platformChatGPT · Codex · Claude Code
- Cost
- Free, no paid service needed
- Setup effort
- Medium · a few setup steps
- You'll need
- Typical use
- A security engineer receives an internal Electron desktop app, unpacks the ASAR, audits webPreferences and preload bridges, and produces a remediation report.
- Not a fit if
- Users who need a GUI and avoid the terminal
- Teams wanting one-click cloud scanning without local setup or optional external tools
- Users who intend to test systems without authorization
- Website
- ptn1411.github.io ↗ set on GitHub
- Maintenance
- Commits in the last 30 dayslast commit 2026-11-07
- Source review
- 41/100 · Major gaps
What does this agent do, and when should you use it?
This repository combines a Python CLI toolkit with AI Agent skill instructions for authorized software and infrastructure auditing. Its entry points are scripts/full_assess.py and scripts/orchestrate.py, which classify a target (IP, web URL, binary, bundle, sourcemap) and dispatch to the matching skill chain. Dedicated subdirectories cover binary identification, Electron unpacking and configuration analysis, JavaScript sourcemap recovery, Android APK static analysis, SBOM and supply-chain review, Docker/Kubernetes/Terraform/cloud configuration checks, passive web recon, an integrated Nmap scanner, Windows Event Log threat hunting, and CVE/exploit intelligence lookup across CISA KEV, FIRST EPSS, NIST NVD, Exploit-DB and GitHub PoC sources. Each skill is self-contained with its own SKILL.md, scripts/ and references/, and outputs structured reports with severity ratings and remediation guidance into output/. The project provides both a link_skills.py synchronizer for AI Agent global config directories and standalone Python scripts that can be run without any agent.
The toolkit is a set of independent Python CLI scripts that read local files, URLs, or network targets and write structured reports. scripts/orchestrate.py and scripts/assess.py classify a target path or URL (IP, web URL, binary, file bundle, sourcemap) and invoke the corresponding skill scripts; --dry-run previews the dispatch. binary-identifier/scripts/identify_app.py reads a binary and emits language, compiler, packager and framework fingerprints. electron-builder-unpacker/scripts/unpack_electron_builder.py unpacks Electron/ASAR bundles, and electron-app-analyzer/scripts/analyze_electron.py audits IPC, webPreferences and preload bridge configuration. javascript-deobfuscator/scripts/extract_sourcemap.py restores JS source from .map files, and android-apk-pentester/scripts/analyze_apk.py performs static analysis of APK/XAPK packages. vulnerability-lookup/scripts/lookup_vuln.py queries CISA KEV, FIRST EPSS, NIST NVD, Exploit-DB and GitHub PoC sources for a CVE, while searching-exploit-db/scripts/search_exploit_db.py searches a local Exploit-DB copy. container-cloud-auditor/scripts/analyze_container_cloud.py inspects Dockerfiles, Kubernetes YAML, Terraform and cloud configs, and sbom-supply-chain-auditor/scripts/analyze_supply_chain.py builds an SBOM, audits dependencies and flags dependency-confusion or malicious packages. web-app-scanner/scripts/web_recon.py performs passive recon (security headers, TLS, CORS, endpoint leaks), with sqli_test.py gated behind --authorized; network-scanner/scripts/nmap_scan.py wraps Nmap. windows-log-hunter/scripts/hunt_eventlog.py hunts local Windows Event Logs. All results are written under output/ with severity grading and defensive remediation suggestions.
- A security engineer receives an internal Electron desktop app, unpacks the ASAR, audits webPreferences and preload bridges, and produces a remediation report.
- A DevOps team runs container-cloud and SBOM supply-chain audits on Dockerfiles, Kubernetes YAML and Terraform before a release, generating dependency and SBOM evidence.
- A red or blue team with written authorization looks up CVE-2024-6387 or CVE-2021-44228 and aggregates CISA KEV, EPSS, NVD and Exploit-DB intel without executing exploits.
- A mobile security analyst statically inspects an internal APK/XAPK for permissions, components and misconfigurations without running the app.
- A Windows incident responder hunts local Event Logs for suspicious accounts, log clearing and attack traces using windows-log-hunter.
- An AI Agent user syncs the whole skill set into Claude Code or Gemini CLI so the agent can call the scripts inside an audit workflow.
How do you install or deploy this agent?
Python 3.10 or newer is required. Clone the repository and install Python dependencies:
git clone https://github.com/ptn1411/skill.git
cd skill
python -m pip install -r requirements.txtTo sync all skills into the global config directories of supported AI Agents (recommended on Windows):
python scripts\link_skills.pyOr create an NTFS directory junction:
python scripts\link_skills.py --mode junctionExternal tools (Node.js, asar, Android SDK, JADX, Nmap, ilspycmd) are only needed for the workflows that use them; see TOOLS.md. Manifest configuration for other CLI agents (Codex, OpenAI) is documented in INSTALL.md.
How do you use this agent?
The primary entry point is the orchestration script, which classifies the target and runs the matching chain:
python scripts\full_assess.py https://app.example.com --out output\assessment
python scripts\full_assess.py 192.168.1.10 --out output\assessment
python scripts\orchestrate.py "C:\path\to\owned-app.exe" --out output
python scripts\orchestrate.py "C:\path\to\app-folder" --out output
python scripts\assess.py example.com --dry-runVulnerability intelligence and Exploit-DB search:
python vulnerability-lookup\scripts\lookup_vuln.py --cve CVE-2024-6387
python vulnerability-lookup\scripts\lookup_vuln.py --cve CVE-2021-44228 --out output\cve-report
python searching-exploit-db\scripts\search_exploit_db.py --cve CVE-2021-44228
python searching-exploit-db\scripts\search_exploit_db.py --query "OpenSSH 9.8"Container, cloud and supply-chain audits:
python container-cloud-auditor\scripts\analyze_container_cloud.py . --out output\container-cloud
python sbom-supply-chain-auditor\scripts\analyze_supply_chain.py . --out output\sbomWeb recon, controlled SQLi testing and network scanning:
python web-app-scanner\scripts\web_recon.py https://example.com --out output\web-recon
python web-app-scanner\scripts\sqli_test.py "https://example.com/item?id=1" --authorized
python network-scanner\scripts\nmap_scan.py 192.168.1.0/24 --profile quick --out output\nmapBinary, Electron, sourcemap, APK and Windows log workflows:
python binary-identifier\scripts\identify_app.py target.exe
python electron-builder-unpacker\scripts\unpack_electron_builder.py app-dir --out output\electron-unpacked
python electron-app-analyzer\scripts\analyze_electron.py output\electron-unpacked --out output\electron-analysis
python javascript-deobfuscator\scripts\extract_sourcemap.py "https://example.com/app.js.map" output\recovered-js
python android-apk-pentester\scripts\analyze_apk.py app.apk --out output\apk-analysis
python windows-log-hunter\scripts\hunt_eventlog.py --out output\huntRegression tests and skill contract validation:
python -m unittest discover -s tests -v
python orchestrator-plugin-sdk\scripts\validate_skill_contract.py container-cloud-auditorWhat are this agent's strengths and limitations?
- Ships both AI Agent skill instructions and standalone Python CLIs, so the same workflows run inside Claude Code / Gemini CLI or directly from a terminal
- Broad coverage: binary fingerprinting, Electron unpacking and config analysis, sourcemap recovery, APK static analysis, SBOM, container/cloud config checks, web recon, Nmap, Windows Event Logs and CVE intelligence
- Orchestration scripts (orchestrate.py, full_assess.py) auto-dispatch by target type and offer a --dry-run preview
- CVE lookup aggregates CISA KEV, FIRST EPSS, NIST NVD, Exploit-DB and GitHub PoC sources without downloading or running exploits
- Includes a MASTER_POLICY.md authorization boundary and a regression/contract test workflow that keeps skills consistent
- link_skills.py syncs skills into AI Agent config directories in one command, with a Windows junction mode
- Several workflows depend on external tools (Node.js, asar, Android SDK, JADX, Nmap, ilspycmd), increasing setup effort
- README examples and link_skills.py are PowerShell-oriented, so cross-platform users must adapt paths and commands
- License is listed as unknown, so redistribution and commercial use terms need to be verified first
- Requires Python 3.10+ and does not document an official packaged release or container deployment path
- Primary documentation is in Vietnamese, adding a reading burden for non-Vietnamese users
- No standard packaging for a specific Agent platform is described; integration depends on each agent's own manifest format
How does this agent compare with similar options?
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| Authorized Artifact Auditor This agent | 41 · Major gaps | CLIFree | ★ 327 | 14d ago | Python | ChatGPT · Codex · Claude Code |
| Flounder Security Auditor | 75 · Good | CLI | ★ 527 | 6d ago | TypeScript | Codex · Claude Code |
| PentestCode | 45 · Major gaps | CLIFree + model costs | ★ 1.2k | 16d ago | TypeScript | OpenAI API · Claude API |
| Semia — Security Audit for AI Agent Skills | 66 · Some gaps | CLIFree + model costs | ★ 614 | 5mo ago | Python | Codex · Claude Code · OpenAI API · Claude API |
How does FollowAgents rate this agent?
Why each dimension lost points
The README and root SKILL.md emphasize authorized scope, prohibit access-control circumvention, and call for confirming target, methods, data handling, and stop conditions before scans. However, the sampled anti-debugging skill gives concrete steps, code, and broad tool permissions for bypassing protections in commercial software, weakening least privilege and confirmation safeguards. The Android workflow can install apps, inject a CA, set a proxy, and generate hooks; it recommends a dry run but the sample does not show consistent step-by-step confirmation or rollback. Secret redaction is promised, but explicit data-flow, storage/deletion controls, and dependency vulnerability mitigation are not demonstrated. An upstream source is named, while maintenance responsibility and update path remain unclear, so these criteria receive partial credit.
The README's CLI, test, and skill structure is corroborated by sampled test files. The root skill excerpt ends mid-policy, however, and the anti-debugging sample conflicts with its stated boundaries. requirements.txt specifies minimum versions and optional external tools but shows no pinning or availability strategy. The sample does not demonstrate user-facing failure messages or recovery guidance, so failure_messages scores 0.
The repository describes distinct use cases across binaries, web/network, Android, cloud configuration, dependencies, and Windows logs, and distinguishes static analysis from optional network routing. The root skill also prohibits expanding a single-target request to other hosts. Yet tool instructions mix static review with dynamic and bypass operations, and trigger descriptions and authorization gates are not consistent throughout. Python requirements and some platform commands are documented, but installation examples lean toward Windows, so environment fit is partial.
The README provides a clear project map, installation guidance, common commands, test and contribution workflows; sampled skills include purposes, workflows, outputs, limitations, or examples. Naming and language conventions vary, and the samples place a skill called 'authorized' alongside 'pentester' and 'bypass' material. No license information or version/change history is shown. Contribution steps exist, but no accountable maintainer or maintenance arrangement is identified.
Structured reports, severity and remediation guidance, and redacted secret locations support usable outputs. The dispatcher, multiple audit areas, and scripts provide meaningful combined capability. The breadth brings substantial external-tool and emulator/interception setup costs, and the sample does not provide enough evidence to quantify accuracy or routine benefits, so the cost-benefit case is only partially supported.
README commands, installation, tests, and skill entry points are traceable, and sampled tests correspond to some tool behavior. Many capability statements remain project claims; the packet does not cover every implementation, and the sampled sources do not consistently corroborate the key safety boundaries. Documentation usually distinguishes purpose, limitations, and examples, and tests can be recognized as source evidence; this assessment does not claim that anything was run or independently verified.
- The sampled anti-debugging skill contains actionable methods to bypass checks and hide a debugger, creating direct tension with the root skill's stated prohibition on circumvention; verify actual routing and authorization gates before use.
- Android installation, CA injection, proxy configuration, and Frida hooks can change the test environment or create traffic/capture data; confirm target, device, output location, and cleanup approach first.
- License metadata is unknown, and the samples show no dependency lock, changelog, or explicit maintenance owner; do not infer usage rights or maintenance status.
FAQ
Does using this project cost money?
Can I point it at systems I do not own?
Will it download and run exploits automatically?
Which AI Agents does it integrate with?
Does my data leave the machine?
Is Authorized Artifact Auditor open source?
Is Authorized Artifact Auditor safe to use?
Is Authorized Artifact Auditor still maintained?
Who makes Authorized Artifact Auditor?
What is Authorized Artifact Auditor's official website?
Thanks — we use this to improve the page.