Skip to content

Fix three broken internal links #116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
vpetersson-bot wants to merge 1 commit into from
Closed

Fix three broken internal links #116

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/compliance/fda-medical-device.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ sbomify ships an **FDA Medical Device (2025)** plugin that grades each uploaded

## Additional Resources

For more details, see our [FDA Medical Device SBOM Requirements guide](/blog/fda-medical-device-sbom-requirements/).
For more details, see our [FDA Medical Device SBOM Requirements guide](/2026/01/09/fda-medical-device-sbom-requirements/).

## Official Source

Expand Down
2 changes: 1 addition & 1 deletion content/faq/why-do-i-need-an-sbom.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ SBOMs are increasingly required by law and industry standards:
- **[EU Cyber Resilience Act (CRA)](/compliance/eu-cra/)** - Requires SBOMs for all products with digital elements sold in the EU
- **[NTIA Minimum Elements](/compliance/ntia-minimum-elements/)** - US government baseline for SBOM content
- **[NIST 800-171](/compliance/nist-800-171/)** - Supply chain risk management requirements
- **[FDA guidance](/compliance/fda/)** - Medical device manufacturers must submit SBOMs
- **[FDA guidance](/compliance/fda-medical-device/)** - Medical device manufacturers must submit SBOMs
- **[PCI DSS 4.0](/compliance/pci-dss/)** - Payment industry now references software composition analysis

See our full [Compliance guide](/compliance/) for details on each framework.
Expand Down
2 changes: 1 addition & 1 deletion content/posts/2026-01-23-announcing-sbomify-v0-25-the-one-with-attestations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ Knowing when your software reaches end-of-support or end-of-life is critical for

You can set these dates manually in the UI for both **products** and **components**. This is useful for tracking your own release schedules and support commitments.

For common Linux distributions and frameworks, lifecycle data can also be added automatically. The [Lifecycle Database](/blog/2026/01/20/announcing-sbomify-action-v0-11-the-one-where-they-go-to-pypi/#know-when-your-software-goes-end-of-life) in sbomify-action embeds CLE data directly into your SBOMs during generation. This covers distributions like Ubuntu, Debian, Alpine, and Fedora, as well as language runtimes and frameworks including Python, Go, Django, Rails, and React.
For common Linux distributions and frameworks, lifecycle data can also be added automatically. The [Lifecycle Database](/2026/01/20/announcing-sbomify-action-v0-11-the-one-where-they-go-to-pypi/#know-when-your-software-goes-end-of-life) in sbomify-action embeds CLE data directly into your SBOMs during generation. This covers distributions like Ubuntu, Debian, Alpine, and Fedora, as well as language runtimes and frameworks including Python, Go, Django, Rails, and React.

These dates flow through to your Trust Center and can be displayed on public product pages. For organizations subject to regulations like the [EU Cyber Resilience Act](/compliance/eu-cra/), tracking lifecycle information is a requirement.

Expand Down
Loading