Community
Contribute blueprints for the CRA reproduce leg, and share how manufacturers run product inventory and Article 14 readiness.
Community Blueprint Contribution
Blueprints are how a release gets rebuilt years after it shipped. Every board covered by a community blueprint is one more product whose maintainer can reconstruct the original toolchain when a patch becomes mandatory.
- • Submit blueprints via pull request
- • Follow blueprint authoring guidelines
- • Get your blueprint verified by the alloy-it team
- • Help maintain and improve existing blueprints
Verified Blueprint Program
Blueprints that meet our quality and security standards receive a "Verified" badge. Verified blueprints are:
- • Regularly tested and updated
- • Security scanned for vulnerabilities
- • Documented with clear requirements
- • Maintained by the alloy-it team or trusted contributors
Roadmap and Changelog
Product inventory, continuous scanning, component triage, firmware-derived SBOMs, the Article 14 awareness clock and SRP export, advisories, and per-release evidence packs are all shipped. What we are still working on:
In progress
- • CI-attested build provenance, so a rebuild target is backed by an attestation rather than a typed reference
- • A richer browser for deep-analysis reports
- • Broader embedded firmware format coverage
Follow releases on GitHub for the current list.
Get Involved
Discussions
Ask questions, share ideas, and connect with other embedded engineers
Join the discussion →Need something the community does not cover?
Start free with a product, or contact us.