What should you check before adding a new dependency?
Ten quick questions to ask before adding a package: purpose, publisher, install scripts, age, sources and fallback. Five minutes now can avoid weeks later.
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.
Ten quick questions to ask before adding a package: purpose, publisher, install scripts, age, sources and fallback. Five minutes now can avoid weeks later.
Retention rules match tags, so design tags for them: a class prefix, a version, and a build id. A scheme that works with ECR, Harbor and Artifact Registry.
Switching dependency scanners without losing coverage takes a parallel period: align inputs, compare a sample, restate your baseline, then cut over.
A suppressed finding returns when reported under another ID for the same flaw. How aliases work and how to key suppressions so they keep matching.
A suppression record needs advisory ID, scope, reason, evidence, owner, approver and dates. Field list, a YAML example and a CI check for bad entries.
Set two numbers per rollout group: a success level that unlocks the next group and an error level that stops the whole rollout. How to pick them.
A low-effort checklist for instructors and TAs to check student and capstone projects for vulnerable dependencies without turning grading into an audit.
Keep the p12 and profile as encrypted CI secrets, use a temporary keychain on the runner, limit which jobs read them, and clean up self-hosted runners.
Small files go in as base64 secrets. Over 48 KB, GitHub suggests encrypting the file and storing the passphrase. Masking caveats and safer choices.
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.