Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
Never place github context values such as pull request titles inside run scripts. Pass them via environment variables or an action. Examples and checklist.
Never pass user supplied URLs straight to res.redirect. Parse the URL, compare the host to an allow list, and prefer fixed route names. Steps and a test.
Good postmortem actions cover prevention, detection and mitigation, each with an owner, a priority and a tracking ticket. How to write and balance them.
A one week checklist for the supply chain part of a first enterprise security call: inventory, scan evidence, owners and honest gaps, ready to share.
Prefect blocks have typed fields, and SecretStr fields get extra encryption and are hidden in the UI. Variables are plain JSON. Use blocks for secrets.
A short pre-release dependency checklist for open source maintainers: audit, lower bounds, lockfile, workflow pins, and notes. Takes about fifteen minutes.
A go-live checklist for vulnerabilities: inventory, scan, ranked findings with owners, approved exceptions and a recorded baseline before launch.
A one-page checklist to run before a low-code app reaches production: owner, identity, data, sharing, input, logging and a way to switch it off.
A one page checklist for merging AI suggested security fixes: reproduce, scope, tests, facts, rescan, rollback and owner. Copy it into your PR template.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.
