A security checklist for Firefox extension developers
Mozilla's secure extension guidance as a checklist: remote code, DOM insertion, CSP, wrappedJSObject, UI, fingerprinting and third-party libraries.
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.
Mozilla's secure extension guidance as a checklist: remote code, DOM insertion, CSP, wrappedJSObject, UI, fingerprinting and third-party libraries.
Use retrieval for facts that change and fine-tuning for behaviour and format. A decision guide with questions to ask and when to combine both.
Quick answers on fine-tuning LLMs: data size, cost, LoRA, RAG, safety, forgetting and evals, each with a link to the longer guide for more detail.
A twelve point checklist for fine-tuning data: sourcing, cleaning, labelling, splitting, privacy and provenance, to run before you spend on training.
A practical search plan for RSA, ECDSA, ECDH and X25519 usage across source, config, certificates and dependencies, before a post-quantum migration.
AuditEvent records that something happened and who did it. Provenance records how a resource came to be. When to use each, and keeping audit honest.
Release, experiment, ops and permissioning flags have very different lifetimes. Knowing which one you have tells you when it should be removed.
Old feature flags hide dead code, untested paths and forgotten access rules. How to inventory, expire and remove flags before they become a risk.
The scan command reports but does not fail the build. A short jq step on the output file adds a severity gate you control, with a note on exit code 2.
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.