delist-after-reconcile-enforcement-8bc64d — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited delist-after-reconcile-enforcement-8bc64d (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.
Domain: extensions-mcp Trigger: Use when an extension or plugin system must enforce removals even if the install or update pass made no additions. Source Pattern: Distilled from reviewed post-sync extension policy enforcement flows.
Apply delist or policy enforcement after synchronization finishes so removal decisions operate on the freshest materialized state. Treat removals as first-class changes that update metrics and propagate the same downstream refresh signal used for installs. This keeps policy enforcement visible and ensures callers reload when the live set changed through removal rather than addition.
If a headless bootstrap finds that one installed extension was later delisted, remove it after registry sync and return a changed signal so the command surface reloads.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.