← All articles
news··Christian Kaman

v0.2.3 — audit precision fixes

Tightens the secret detection regex and excludes build-artifact directories. Two regression tests added. Found by running the audit against our own docs.

What's fixed

Two classes of false positive in audit.sh and gate-check.sh Gate F, both found by running the audit against this documentation site.

1. Build-artifact walking. The scripts walked the filesystem for secret patterns and hit compiled output under .next/, out/, .source/, and .wrangler/. Those directories are gitignored but the scripts weren't excluding them. All four are now in the exclusion regex alongside node_modules/, .git/, and dist/.

2. Pattern over-matching. The regexes matched bare prefixes like sk_live_ and the bare identifier PRIVATE_KEY. Any documentation that mentions these patterns — including our own customization page — tripped the audit. The patterns are now tight:

AWS AKIA[0-9A-Z]{16} and Google AIza[0-9A-Za-z_-]{35} were already tight and unchanged.

Regression tests

Two new tests encode both failure modes:

The test suite is now 10 tests, all passing on macOS bash 3.2 and Ubuntu latest.

Upgrade

cd /path/to/your-speckit-security-clone
git pull
# then reinstall into any affected projects
cd /path/to/project
specify extension remove tekimax-security
specify extension add --dev /path/to/speckit-security

Or on the releases page.

The full story of how we found the bugs is in the blog post "Launching speckit-security" — the short version is: we audited our own documentation site and the audit flagged itself.