Dive into a new Pentesting Experience with
Athena OS

🏅Born for InfoSec Professionals, Bug Bounty Hunters, Passionate Students and Spicy Hackers🏅

💞 Get Athena OS Now! 💞

Click Docker icon above to explore Athena OS Docker containers!

Click the icon above to explore Athena OS WSL in Microsoft Store App!

Automated Package Updates

Packages in this repository are kept up to date automatically via a daily GitHub Actions workflow powered by nvchecker.

How it works

The automation runs every day (and can also be triggered manually) and goes through the following steps:

1. Config generation — .nvchecker/generate-nvchecker-config.py scans every PKGBUILD under src/ and auto-generates .nvchecker/nvchecker.toml. Each package is classified as one of:

   • Release package — has a static pkgver= and a remote source URL. Tracked by latest tag/release on the hosting platform.
   • VCS package — has a pkgver() function and a git+https:// source. Tracked by latest upstream commit.
   • Local-only package — all sources are local files. Skipped silently (no upstream to track).

2. Version check — nvchecker queries the upstream of every tracked package and writes the results to .nvchecker/newver.json. This is compared against .nvchecker/oldver.json (committed in the repo) to find packages that have a new version available.

3. PKGBUILD update & PR — for each outdated package the workflow:

Supported hosting platforms

Shell variable expansion in PKGBUILDs

The config generator and the CI workflow both resolve shell variable references in source= lines so that indirect URLs like the following are handled correctly:

_pkgname=${pkgname#athena-}
source=("git+https://github.com/Athena-OS/$_pkgname.git")

The following bash parameter expansion forms are supported:

Known limitations

The following bash constructs are not resolved by the automation. PKGBUILDs that rely on them will be skipped gracefully with an informational note — no error is raised, and they can always be updated manually.

If your PKGBUILD uses any of the above and the automation skips it, you can either rewrite the assignment as a plain var=value line or open a PR updating the version manually.