security-advisory-compat-enforcer

Featured

Review a GitHub security advisory and safely update .github/aw/compat.json with evidence-backed version enforcement.

Code & Development 5,125 stars 539 forks Updated today MIT

Install

View on GitHub

Quality Score: 90/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Security Advisory Compatibility Enforcer Use this skill to translate a GitHub repository security advisory into the smallest safe update to `.github/aw/compat.json`. ## Required inputs Record the repository, GHSA identifier, requested enforcement policy, and any patched version supplied by the user. Treat a user-supplied version as a target to verify, not as evidence for advisory details. ## Evidence retrieval 1. Attempt authenticated retrieval first: `gh api repos/OWNER/REPO/security-advisories/GHSA-ID`. 2. If authentication is unavailable or access fails, try the public global advisory endpoint: `gh api advisories/GHSA-ID` (or its equivalent REST URL). 3. Record the endpoint and outcome of each attempt. If both sources are inaccessible, state that explicitly. Never infer or invent the affected package, vulnerable range, severity, CVE, publication state, or patched version. 4. Verify the proposed patched version independently. Prefer a published repository release or tag, then package-registry metadata when applicable. Cite the exact URL or command result. Do not update compatibility policy if the target cannot be verified, unless the user explicitly directs use of a supplied target despite inaccessible advisory metadata; document that limitation without converting it into fabricated advisory evidence. ## Choose the correct policy field - `minimumVersion` is a hard floor: activation fails for every compiler version below it. Change it...

Details

Author
github
Repository
github/gh-aw
Created
1 years ago
Last Updated
today
Language
Go
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

rust-security

Use when you audit Rust dependencies with cargo-audit, configure or change a cargo-deny policy in deny.toml, triage a RUSTSEC advisory, evaluate a new crate for typosquat and supply-chain risk before you add it to Cargo.toml, respond to a published CVE on a pinned dependency, decide whether an advisory ignore entry is acceptable, or harden a Rust parser that reads untrusted files. Triggers on "cargo audit", "cargo deny", "deny.toml", "RUSTSEC", "advisory", "supply chain", "typosquat", "malicious crate", "yanked", new-dependency-addition reviews, and archive, backup, or binary-format parser hardening.

2 Updated 1 weeks ago
po4yka
AI & Automation Listed

change-dependencies

Change external libraries, frameworks, SDKs, runtimes, compilers, or build tools with verified compatibility and bounded scope. Use when an authorized change adds, upgrades, downgrades, replaces, or removes a dependency, including CVE remediation. Do not use for internal imports, inventory or advice only, or wholesale stack replacement.

4 Updated 2 days ago
dayfinggg
Code & Development Listed

github-policy

Use when a repository's branch protection, rulesets, required checks, or PR-run cancellation may not match the canonical policy — a new repo that was never set up, a repo somebody configured by hand, an org whose repos were never brought into line, or a merge that was blocked or allowed in a way nobody expected. Also for: is this repo actually protected, why did that PR merge without CI, why is every PR asking me to update the branch, bring these repos into compliance, set up branch protection, audit my rulesets, apply the policy to all my repos, organization ruleset, convert classic branch protection to a ruleset, required approvals, cancel superseded PR runs.

2 Updated today
Tamircohen28