composer-update — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited composer-update (Agent Skill) and scored it 91/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 1 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
The text {match} is the classic direct prompt-injection phrasing. Placed in a skill body that the agent reads as trusted instructions, it tries to make the agent abandon its prior rules and follow whatever comes next — a full system-prompt override.
ignore/disregard/forget … previous instructions sentence.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.
Analyze dependency updates after composer update, detect conflicts, and summarize relevant changes.
composer update if availablecomposer.lock with the previous versionold → newcomposer.json vs composer.lock)For each updated package:
vendor/<package>/CHANGELOG*composer validatecomposer auditUse the template defined in templates/update-report.md.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.