07-deploy-after-changes — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited 07-deploy-after-changes (Rules) 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.
description: After substantive edits, commit, push, and deploy—Vercel for landing, deploy.ps1 for production server alwaysApply: true
When you change production-facing code, do not stop at “saved locally”—commit, push, and deploy so the user does not have to deploy manually.
veridion-landing/)veridion-api/):npx vercel --prod --yes
veridion-landing/ (wrong root / doubled path)..cursor/rules/06-veridion-landing-vercel.mdc.deploy.sh targets, MCP server (everything else that ships to the VPS) $env:DEPLOY_HOST = 'root@YOUR_REAL_IP_OR_HOSTNAME'
.\deploy.ps1deploy.ps1 pushes then runs ssh $env:DEPLOY_HOST "cd /opt/veridion-nexus && ./deploy.sh".
DEPLOY_HOST is unset, the script still pushes but does not SSH—tell the user to set it once per session or in their profile..md comment-only: deploy optional unless the user wants it.veridion-landing/ changes and `deploy.ps1` for server-side changes (both if both apply).~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.