Install
$ agentstack add skill-yue-zhou1-zkcrypto-audit-dependency-auditor ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
dependency-auditor
Domain auditor for crypto dependency hygiene and supply-chain risk.
When to Use
- Auditing lockfiles and dependency graphs for vulnerable cryptographic crates/libs
- Reviewing security-significant feature-flag semantics
- Checking transitive dependency duplication and semantic drift
- Validating fork provenance and patch divergence from upstream
When NOT to Use
- Primitive-level cryptographic correctness audits without dependency concerns
- Runtime side-channel analysis detached from dependency configuration
- Declaring dependency risk confirmed without advisory and code-path verification
Core Review Areas
- Dependency lockfile completeness and version provenance
- Advisory coverage for direct and transitive crypto dependencies
- Security-significant feature-flag behavior
- Fork provenance, patch drift, and vendored dependency auditability
- Toolchain/MSRV drift and duplicate crypto stack semantics
Workflow
Phase 1: Graph and inventory
- Read
references/dependency-checklist.md - Execute
workflows/advisory-review.md - Enumerate direct/transitive crypto dependencies and active feature sets
Phase 2: Advisory and feature review
- Compare dependency graph against known advisories/changelogs
- Validate security semantics for enabled/disabled feature-flag combinations
- Identify duplicate crates/libs with incompatible behavior expectations
Phase 3: Pattern hunt
- Read
references/finding-patterns.md - Prioritize vulnerable transitive pins, feature regressions, and stale fork drift
Phase 4: Handoff
- Send surviving findings to
crypto-fp-check - Use
zkbugs-indexonly after the finding survives verification
Output Contract
Produce a dependency-specific handoff that includes:
- The affected dependency path (direct/transitive/fork)
- The advisory, feature-flag, or provenance invariant at risk
- Whether the issue is versioning, feature semantics, duplicate stacks, or fork drift
- The next verification or reporting route
Reference Index
- [references/dependency-checklist.md](references/dependency-checklist.md)
- [references/finding-patterns.md](references/finding-patterns.md)
- [workflows/advisory-review.md](workflows/advisory-review.md)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Yue-Zhou1
- Source: Yue-Zhou1/zkcrypto-audit
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.