rebuild-plugins-before-deploy — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited rebuild-plugins-before-deploy (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.
Directus plugins must be rebuilt from source (plugins/) before every deployment. If you deploy without rebuilding, the extensions directory will contain stale or missing builds, and the server will start normally but custom endpoints, hooks, and interfaces will silently not work. There is no error message — the server looks healthy but custom functionality is missing.
npm run deploy, directus deploy, Docker build)plugins/ have been modified since last buildextensions/ directory exists in the projectplugins/ have changed since the last buildnpm run build (or pnpm build) in each plugin directory under plugins/dist/ folderextensions/ (or verify the build outputs directly there)The server starts successfully, returns 200 on healthcheck, logs show normal startup. But custom API endpoints return 404, custom hooks don't fire, custom interfaces don't render. There is NO error in the logs. Diagnosed after 2h of debugging on 3 independent sessions. The root cause each time: plugins were modified but not rebuilt before deploy.
extensions/ is auto-generated — it must be explicitly populated from plugin builds~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.