bump-version — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited bump-version (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Two phases: (1) bump commit, always; (2) tag + push, only on explicit instruction.
User override always wins. Accept any of:
major, minor, patchbump to 1.0.00.9.0a1, 0.9.0rc1Without override, inspect commits since the last tag:
git describe --tags --abbrev=0 # last tag, e.g. v0.8.0
git log <last-tag>..HEAD --oneline # commits to classifySemVer rules:
Bias toward patch over minor, minor over major when ambiguous.
pyproject.toml: one line change:
version = "X.Y.Z"uv.lock: run from repo root after editing pyproject.toml:
uv lockUpdates only the self-referential [[package]] name = "goodeye" entry. No dependency upgrades occur.
Stage exactly these two files:
git add pyproject.toml uv.lockCommit message (no body):
chore: bump version to X.Y.ZOnly proceed if the user explicitly says to tag, push, release, or publish (e.g. "tag it", "push the tag", "ship it to PyPI").
Verify the tag doesn't already exist, then:
git tag vX.Y.Z
git push origin vX.Y.ZThis triggers publish.yml -> builds wheel -> publishes to PyPI via OIDC trusted publishing. No manual credentials needed. Monitor at github.com/Goodeye-Labs/goodeye-cli/actions.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.