release — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited release (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.
End-to-end release workflow for vercel-plugin.
Run all gates in parallel:
bun run typecheck # tsc --noEmit on hooks/src
bun test # all test files
bun run validate # skill frontmatter + manifest integrityStop if any gate fails. Fix issues before proceeding.
Read the current version from .plugin/plugin.json. Ask the user which semver component to bump if not specified:
| Bump | When |
|---|---|
| patch | Bug fixes, test/fixture updates, docs |
| minor | New skills, new hooks, new features |
| major | Breaking changes to hook API or skill map |
Default to patch if the user says "release" without specifying.
Update the version field in .plugin/plugin.json. This is the only version source of truth.
bun run build # hooks (tsup) + manifestThis compiles hooks/src/*.mts → hooks/*.mjs and regenerates generated/skill-manifest.json.
git add -A
git commit -m "<summary>; bump to <new-version>"
git pushCommit message style: match existing convention — descriptive summary followed by ; bump to X.Y.Z (see git log for examples).
The pre-commit hook will re-run typecheck and recompile hooks automatically. If it fails, fix the issue and create a new commit (never amend).
.plugin/plugin.json — the version field. There is no package.json version to sync.
.plugin/plugin.json version bumpedbun run build succeeded~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.