Cyfrin

Aderyn retirement

Retirement status, retained documentation, and guidance for existing Aderyn users

Aderyn has been retired and is no longer maintained. This includes the CLI, VS Code extension, and GitHub CI Assistant. There will be no further maintenance or security updates from Cyfrin.

This documentation stays online as a reference for existing projects and historical analysis. Source history and technical documentation remain available; they do not imply ongoing support or a recommendation to start using Aderyn.

Installation and download status

The following status was checked on 14 November 2026:

ChannelRetirement status
GitHub releasesOfficial CLI installation artifacts and extension VSIX downloads have been withdrawn. Retained shell installer URLs print a retirement notice and exit with an error. Source history and source/checksum records remain available.
CyfrinupNo longer installs or updates Aderyn. The shared installer continues to support SafeHash.
HomebrewThe Aderyn formula is disabled. The shared Cyfrin tap remains available for other tools.
crates.ioAll published versions of the retired Rust packages are yanked. Existing lockfiles and crate archives can remain usable.
npmAll versions of @cyfrin/aderyn are deprecated. Package archives remain accessible, but their installer references withdrawn GitHub binaries.
VS Code MarketplaceThe extension is unpublished. Previously published VSIX files remain accessible through some download endpoints; delisting does not remove installed extensions.
Open VSXThe known extension listing and download endpoints have been removed.
GitHub Action MarketplaceThe CI Assistant listing has been removed. References to repository tags or commit SHAs are not disabled by delisting.

Existing binaries, installed extensions, cached images, forks, and previously downloaded archives are not remotely removed. Fresh installations, updates, or CI runs that depend on withdrawn downloads may fail.

Remove the CLI

Use the package manager that installed your copy. Run only the command that matches your installation method:

Homebrew

brew uninstall aderyn

Global npm installation

npm uninstall -g @cyfrin/aderyn

For a project-local npm dependency, run npm uninstall @cyfrin/aderyn in that project and commit the package manifest and lockfile changes.

Cargo installation

cargo uninstall aderyn

Standalone Cyfrinup or release-installer installation

First locate the executable with command -v aderyn. For a standalone installation in the standard locations, remove only the Aderyn binaries:

rm -f "${CARGO_HOME:-$HOME/.cargo}/bin/aderyn" "${CARGO_HOME:-$HOME/.cargo}/bin/aderyn-update"
rm -f "$HOME/.cyfrin/bin/aderyn"

If you used a custom installation directory, remove its Aderyn executable and updater instead. Keep shared Cargo/Cyfrin directories and other tools. Project configuration, saved reports, and historical records can be retained.

Restart your shell and run command -v aderyn again to check for another copy on your path.

Remove the editor extension

Open the editor's Extensions view, find Aderyn, select Uninstall, and reload if prompted. Check any other profiles and remote environments where the extension was installed.

For VS Code installations with the code command available, you can also run:

code --uninstall-extension Cyfrin.aderyn

Uninstall any separate CLI installation using the instructions above.

Remove or replace CI integrations

Find workflow steps using Cyfrin/aderyn-ci, including tag and commit-SHA references, and remove or replace those steps. Also check shell commands, Docker builds, tool-manager pins, and scripts that install or invoke aderyn or aderyn-update.

Review downstream steps that consume Aderyn reports or expect its check results. If you remove an Aderyn-only job, update required status checks so pull requests are not left waiting for a check that no longer runs. Choose and validate a maintained analysis tool for your project's requirements before treating it as a replacement.

Keep historical audit reports, source references, and reproducibility records where needed. The CLI, configuration, and internals pages remain available for understanding past results.