aztec vs auditsentry
aztec is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑27.
aztec is a plugin bundle for AI coding tools published by critesjosh. No marketplace we read lists it any more. auditsentry is a plugin bundle for AI coding tools published by Iktok Security Labs. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-27. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace critesjosh/aztec-claude-plugin | Removed on 2026-10-27 Version: 2.1.0 Forks (GitHub): 1 Stars (GitHub): 11 Not marked · First seen |
Not listed |
| Community marketplace iktok90-design/ai-smart-contract-auditor | Not listed | Listed Version: 1.0.0 Forks (GitHub): 5 Stars (GitHub): 36 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | aztecno longer listed · | auditsentry |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 11 | 36 |
| Forks (GitHub) (differs) | 1 | 5 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@aztec/mcp-server) | Installs as a plugin bundle |
| Transport | Not stated | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 12, secrets among them: 5 |
| Hooks it runs (differs) | Not published | 2 |
| Parts of the bundle (differs) | 4 | 128 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/critesjosh/aztec-claude-plugin | github.com/iktok90-design/ai-smart-contract-auditor |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-15 | 2026-10-21 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of aztec
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
AI skills for building fullstack Aptos dApps — Move smart contracts, TypeScript SDK, wallet integration, security auditing, and gas optimization.
-
Specialized agents for blockchain development, smart contracts, and Web3 applications
-
OpenZeppelin Solidity Contracts
Access to OpenZeppelin Solidity Contracts.
-
Access to OpenZeppelin Stylus Contracts.
-
Smart-contract security audits for EVM chains and DAML: quote, run and fetch reports.
-
Browser Solidity compiler IDE - smart contract development testing deploy
What each says it does
aztec
Claude Code plugin for Aztec smart contract and application development
auditsentry
AI-powered smart contract security auditor for Claude Code — vuln detection, exploit PoCs, mainnet-fork sims, audit cards, on-chain certificates.
How to run each
aztec
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
auditsentry As a Claude Code plugin
/plugin marketplace add iktok90-design/ai-smart-contract-auditor
/plugin install auditsentry@auditsentryCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only aztec asks for
AZTEC_DEFAULT_VERSION
Only auditsentry asks for
ARBISCAN_API_KEY (secret)BASESCAN_API_KEY (secret)BERATRAIL_API_KEY (secret)ECHIDNA_PATHETHERSCAN_API_KEY (secret)HALMOS_PATHMEDUSA_PATHMYTHRIL_PATHSLITHER_PATHTENDERLY_ACCESS_KEY (secret)TENDERLY_ACCOUNTTENDERLY_PROJECT
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: aztec · What it can do: auditsentry · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.