go — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited go (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.
Verify the work in a real browser instead of trusting that it compiles. Use whichever browser tooling is available and fits the check best.
Easy to miss:
A login wall is not a reason to stop. Prefer a browser where the user is already signed in; that also covers SSO, OAuth and MFA. Otherwise use a test account from the project's seed, fixture or example config, or the user's secrets manager. Do not open, print or search an env file for credentials: if a test login exists only there, load it inside the script that signs in (for example a Playwright script reading process.env), never through chat or tool arguments. On a deployed site a signed-in session is the user's real account, so check without changing data.
If something is broken, fix and verify again; when the same issue keeps failing, ask for direction.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.