SPDX PackageOriginator vs PackageSupplier: who goes in which field?
Supplier is who distributed the package to you, originator is who first created it. See the spec's glibc example and when to use NOASSERTION.
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.
Supplier is who distributed the package to you, originator is who first created it. See the spec's glibc example and when to use NOASSERTION.
Use a git+https URL, add an at sign and a refs/tags or commit pin, and a hash sign for a subpath. Or NONE or NOASSERTION when unknown. Examples inside.
In SPDX 2.3 an ExternalRef line holds category, type and locator. Use PACKAGE-MANAGER for a purl and SECURITY for a CPE. Syntax, examples and mistakes.
DESCRIBES links the SPDX document to the package it covers, and is mandatory when more than one package is present. How to write it and avoid mistakes.
DEPENDS_ON points from consumer to need, DEPENDENCY_OF reverses it, and CONTAINS describes packaging. How to choose, using the spec's definitions.
SPDX has scoped relationships for build, dev, test and runtime dependencies. See when each type fits and why scope changes how you triage findings.
Creator says who or what made the SPDX file, Created is a UTC timestamp, and LicenseListVersion records which license list was used. How to fill each one.
Spark's docs allow credentials inside a repositories URI and warn to be careful. Why that leaks through shells and logs, and what to use instead.
Spark offers SSL and a legacy AES option for RPC encryption. Per its docs SSL is preferred, and AES needs version 2 with GCM to be authenticated.
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.