semantic-versioning — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited semantic-versioning (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.
CHANGELOG.md (e.g., the most recent header ## [X.Y.Z])..github/repository-metadata.json.Scan the changes since the last release:
changelog skill: Look at the items under [Unreleased] or the new version block being prepared.git log: Scan for Conventional Commits types.Follow these priority rules:
! after the type (e.g., feat!:).feat commit or "Added" entry in the changelog.fix, perf, refactor commit or "Fixed"/"Changed" entry in the changelog.docs, chore, style, test, build, or ci changes are found, default to PATCH unless the user specifies otherwise.Update the following files in a single pass:
## [Unreleased] section to ## [NEW_VERSION] - CURRENT_DATE or update the latest entry."version" field.MAJOR.MINOR.PATCH format.CHANGELOG.md is in YYYY-MM-DD format.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.