Skip to content

31 results for “CycloneDX”

ListGrid
What you seeeverything
RecentOldestAddedA–Z
All types31Repos15Articles14Advisories1Write-ups1
“CycloneDX”
endorlabs.comarticle🧠 AI

What is an AIBOM? AI bill of materials explained for security teams | Endor Labs

An AIBOM is a machine-readable inventory of models, datasets, dependencies, AI services, agents and MCP servers, with evidence of origin, license, integrity and evaluation. The Endor Labs explainer walks through a worked CycloneDX example for a fine-tuned support assistant. It compares CycloneDX ML-BOM, SPDX 3.x, the OWASP AIBOM project and the May 2026 CISA/G7 guidance, and lists what an AIBOM cannot show: runtime behavior and agent actions.

CycloneDXSPDXSBOM+5
Endor LabsOWASPCISA+3

ai-policy, ai-infra· Published and added 29 Oct 2026

endorlabs.comarticle🛡️ Security

What is an AIBOM? AI bill of materials explained for security teams | Endor Labs

AIBOM explainer from Endor Labs: an AI bill of materials is a machine-readable inventory of models, datasets, dependencies, AI services, agents and MCP servers, with origin, license and integrity evidence. It walks through a CycloneDX entry for a fine-tuned model, compares CycloneDX ML-BOM, SPDX 3.x, the OWASP AIBOM Generator and the May 2026 CISA/G7 minimum-elements guidance, and lists a six-step build process. It also states what an AIBOM cannot show: model safety, runtime behavior and coding-agent actions.

CycloneDXSPDXSBOM+2
EU AI ActISO/IEC 42001CISA+5

Supply Chain, AI Security, GRC· Published and added 29 Oct 2026

enisa.europa.euadvisory🛡️ Security

ENISA Technical Advisory for Software Bill of Materials

ENISA Technical Advisory for Software Bill of Materials (October 2026, TLP:CLEAR) is non-mandatory guidance for organisations, especially SMEs, starting SBOM adoption. It covers SBOM data models (CycloneDX, SPDX), a mapping of BSI TR-03183-2 fields to CISA minimum elements, lifecycle and CI/CD integration, an SBOM threat model, and security recommendations. It supports Cyber Resilience Act obligations but is not a legal interpretation.

SBOMCycloneDXSPDX
ENISAEU Cyber Resilience ActBSI TR-03183+4

Supply Chain, GRC· Added 23 Oct 2026

endorlabs.comwriteup🛡️ Security

SBOM vs. SBOM: Comparing SBOMs from Different Tools and Lifecycle Stages | Endor Labs

Case study running three open source SBOM generators (two generic, one Maven plugin) on Eclipse Steady 3.2.5 rest-backend at three lifecycle stages (git clone, Maven package, Docker image), yielding 8 CycloneDX SBOMs. Compares precision/recall against the mvn dependency:tree ground truth and finds the Maven-integrated tool perfect (1.0/1.0) while generic tools miss versions, groupIds and transitive dependencies. It also shows PURL qualifier differences (e.g. type=jar, apt qualifiers) make SBOMs hard to compare, test dependencies are indistinguishable, and argues for an SBOM generator benchmark.

SBOMCycloneDXMaven+3
Eclipse SteadyPackage URLNTIA+3

Supply Chain· Published and added 16 Oct 2026

endorlabs.comarticle🛡️ Security

SBOMs are Just a Means to an End | Endor Labs

A critique of the state of SBOM adoption, written by a CISSP product manager at Endor Labs. It argues that the NTIA minimum elements and the SPDX and CycloneDX specs don't require a package URL (purl), so name and version alone can't tell a Maven log4j-core from an npm or cargo package of the same name. It also notes that no spec defines build time, which makes transitive dependency resolution unreliable, and that generation tools place the same data in different fields. It adds that vendors have mixed incentives to ship SBOMs and that practices are immature, and it calls on standards bodies to define required data per prioritized use case.

SBOMSPDXCycloneDX+1
Executive Order 14028NTIANTIA Minimum Elements for an SBOM+2

Supply Chain, GRC· Published and added 16 Oct 2026

endorlabs.comarticle🛡️ Security

Executive Order 14028 SBOM Requirements: What to Comply With and How | Endor Labs

Explains what Executive Order 14028 requires for SBOMs. It covers the NTIA Minimum Elements (seven data fields, automation support, practices and processes) and the SPDX, CycloneDX and SWID formats. It also covers who must comply and how OMB M-26-05 (January 2026) rescinded the standardized self-attestation mandate while agencies can still require SBOMs by contract. It then argues an SBOM is only a starting point and recommends adding reachability analysis, EPSS, VEX and safe-upgrade remediation. The last part promotes Endor Labs.

SBOMSPDXCycloneDX+1
Executive Order 14028NTIANIST+10

GRC, Supply Chain· Published and added 12 Oct 2026

endorlabs.comarticle🛡️ Security

Guide to Implementing Software Supply Chain Security | Endor Labs

Vendor-authored guide that defines a software supply chain as developers, code, dependencies, AI models, containers and CI/CD pipelines. It walks through program components: OSS governance, SAST vs reachability-based SCA, AI model security, SBOM/VEX (NTIA minimum elements, SPDX vs CycloneDX), secrets scanning, CI/CD hardening, and signing/attestation with Cosign/Sigstore. It cites figures such as 95% of vulnerabilities sitting in transitive dependencies and only 1% of SBOMs being fully NTIA-conformant. Each section closes with an Endor Labs product pitch, so treat the framing as vendor-flavoured. The fetched text was truncated, so the final attestation/provenance section was not seen.

Endor LabsSBOMCycloneDX+3
Executive Order 14028NISTCISA+15

Supply Chain, DevSecOps, Learning· Published and added 12 Oct 2026

fossa.comarticle🛡️ Security

Generating and Managing C and C++ SBOMs

A FOSSA blog post explaining why C/C++ SBOMs built from manifest-parsing alone are incomplete, since the ecosystem lacks a centralized package manager and relies heavily on vendored (copy-pasted) source and code snippets. It covers concrete generation paths: Conan's built-in conan.tools.sbom CycloneDX generator, Yocto/OpenEmbedded's native SPDX output via the create-spdx class, process-based tracking for vendored code (third_party/vendor path flagging, manual audits), and the differing snippet-support capabilities of SPDX versus CycloneDX.

SBOMCycloneDXSPDX+3

Supply Chain· Added 1 Oct 2026, published 29 Sep 2026

github.comrepo🛡️ Security

Agent Control Standard (ACS)

Agent Control Standard (ACS) is an OWASP GenAI Security Project specification that lets a separate Guardian Agent inspect an AI agent's proposed actions before they execute and return allow/deny/modify/ask/defer over an authenticated JSON-RPC wire, with OpenTelemetry/OCSF audit trails and a CycloneDX/SPDX/SWID AgBOM inventory. The reference implementation runs Microsoft's Agent Governance Toolkit (AGT) behind the ACS contract with Bun, including host shims for Claude Code and OpenCode, and demonstrably denies a destructive `rm -rf /` command from a live coding-agent session while allowing benign ones. The project is explicit about current gaps — the wire is unauthenticated (issue #70) and the reference Guardian fails open by default (issues #32/#37) — and only 2 of 16 lifecycle hooks are evaluated live in v0.1.0.

BunTypeScriptClaude Code+3
OWASP GenAI Security ProjectAgent Governance Toolkit (AGT)OCSF+1

AI Security· Added 26 Sep 2026

github.comrepo🛡️ Security

git-pkgs — dependency history & supply-chain analysis for git repos

git-pkgs is a Go rewrite of a Ruby tool that adds a git subcommand for tracking dependency changes across a repository's history, indexing manifests/lockfiles from 36+ package managers (npm, RubyGems, Cargo, PyPI, Maven, Composer, Go modules, etc.) into a local SQLite database. Beyond history/blame/diff, it offers supply-chain security commands: `vulns` (OSV-based CVE scanning with SARIF output for GitHub code scanning, plus blame/praise/exposure for remediation metrics), `licenses` (with drift detection and CI-friendly exit codes), `deprecated`, `provenance` (trusted-publishing/attestation checks), `integrity` (lockfile hash drift detection), `maintainers`/`health` (via ecosyste.ms metadata), and `sbom` export in CycloneDX/SPDX. It also supports a dependency-aware `bisect` to find when a vulnerability, license change, or capability (e.g. network access) was introduced, and ships GitHub Actions for CI integration.

npmSBOMOSV+3
CVE-2024-1234PURL

Supply Chain, DevSecOps· Added 25 Sep 2026

endorlabs.comarticle🛡️ Security

How CycloneDX VEX Makes Your SBOM Useful | Blog | Endor Labs

Endor Labs explains how the CycloneDX Vulnerability Exploitability eXchange (VEX) format's analysis sub-field (state, justification, response, detail) lets software publishers communicate real exploitability of SBOM-listed CVEs, cutting through the noise of scanners that flag thousands of largely non-exploitable findings. It walks through each state value (resolved, resolved_with_pedigree, exploitable, in_triage, false_positive) as a machine-readable alternative to ad hoc spreadsheets/portals for vulnerability disclosure, referencing log4shell (CVE-2021-44228) as a case where faster communication would help.

CycloneDXSBOM
CVE-2021-44228

Supply Chain· Published and added 11 Sep 2026

github.comrepo🛡️ Security

ForgeGuardian

ForgeGuardian is an open-source (Apache 2.0) supply chain security scanner covering 9 package ecosystems (npm, PyPI, Go, Maven, RubyGems, Cargo, NuGet, Hugging Face, GitHub Actions) via 8 concurrent scan engines and 223+ built-in malicious-package detection signatures. It runs fully offline/local-first, offers a CLI (fgctl) and self-hosted SOC-style dashboard, generates CycloneDX/SPDX SBOMs, supports Sigstore keyless signing and provenance tracking, policy-as-code rules, dependency topology/attack-surface mapping, drift detection with auto-quarantine, and SARIF output for GitHub Actions CI integration, plus optional AI-powered advisory/patch-agent triage.

npmPyPIGo+3

Supply Chain, DevSecOps· Published and added 5 Sep 2026

github.comrepo🛡️ Security

PackageGuard

PackageGuard is an open-source .NET CLI tool that scans NuGet, npm, pnpm and Yarn dependencies (direct and transitive) across a codebase, enforcing hierarchically-configured allow- and deny-lists for licenses, packages and versions. It scores each package's Legal, Security and Operational risk using signals like OSV vulnerability data, maintainer activity, package signing and release cadence, and can emit a CycloneDX or SPDX SBOM enriched with OSV vulnerability data, plus console, HTML and SARIF output for CI/GitHub code scanning. It's positioned as a free alternative to commercial supply-chain tools like Black Duck and Snyk.

NuGetnpmpnpm+3

Supply Chain, DevSecOps· Published and added 31 Aug 2026

github.comrepo🛡️ Security

vibecheck

vibecheck is a free, open-source, client-side scanner that checks apps built with AI code generators (Lovable, Bolt, v0, Cursor, Claude Code) for common security holes: exposed Supabase Row Level Security / Firebase rules, secrets embedded in the client bundle (Stripe/AWS/DB keys), missing security headers, exposed .env/.git/source maps, unauthenticated LLM proxy or MCP endpoints, and email/TLS misconfigurations. It also scans public repos for cross-tenant IDOR patterns, committed secrets, an OSV.dev supply-chain check, a Dockerfile lint, and generates a CycloneDX SBOM; a companion CLI (tenant-guard) adds a live Postgres cross-tenant isolation test as a CI gate. The project cites CVE-2025-48757 (170+ Lovable apps found with RLS disabled) as motivation.

SupabaseFirebaseOSV+3
CVE-2025-48757IDOR

AppSec, Supply Chain, Mobile Security· Published and added 27 Aug 2026

github.comrepo🛡️ Security

npm-scan

npm-scan is a CLI supply-chain security scanner (@lateos/npm-scan) that inspects npm packages and lockfiles for behavioral attack patterns missed by npm audit/Snyk/Socket, including obfuscated payloads, credential stealers, eBPF kernel rootkits, memory-level OIDC token extraction, GitHub maintainer-account spoofing, and AI-platform-targeted key theft. It ships 23 detectors (D1-D25), validated against real campaigns like IronWorm and Miasma, and outputs SBOM (CycloneDX/SPDX) and SARIF for GitHub Security, plus a workflow to submit critical findings to CISA's VINCE with mandatory manual review. It's free (MIT) for individuals/OSS/evaluation, with paid commercial tiers ($799-$9,900/yr).

npmGitHub ActionsDocker+3
IronWormMiasmaCISA+1

Supply Chain, DevSecOps· Published and added 5 Aug 2026

orca.securityarticle🛡️ Security

Orca Security: AI-BOM

Orca Security explains what an AI-BOM is (an inventory of models, datasets, prompts, embeddings, and external AI services an AI system depends on) and why discovery — not format — is the hard problem: components arrive via notebooks and managed consoles rather than dependency manifests. It surveys the two competing standards, CycloneDX's ML-BOM (v1.7, standardized as ECMA-424 2nd edition) and SPDX 3.0's AI/Dataset profiles, walks through failure modes like unrecoverable model lineage, stale embeddings outliving deleted source documents, and silent version drift on managed endpoints (e.g. Azure OpenAI's auto-update-to-default), and ties the practice to EU AI Act Annex IV technical-documentation requirements and the NIST AI RMF. It ends by describing Orca's agentless SideScanning-based AI inventory across Azure OpenAI, AWS Bedrock, SageMaker, and Vertex AI.

CycloneDXSPDXSBOM+3
EU AI ActNIST AI RMFOWASP AIBOM Generator+2

AI Security, Supply Chain, GRC· Published and added 31 Jul 2026

github.comrepo🛡️ Security

Beetle

Beetle is an offline-first mobile application security platform that statically analyzes Android APKs and iOS IPAs (including Flutter and React Native apps), combining decompilation, taint analysis, secret/endpoint extraction, certificate and native-binary hardening checks, and CVE enrichment with explainable 'intelligence engines' (ownership, confidence, evidence selection, finding fusion) that correlate findings into evidence-backed attack chains. It maps results to OWASP MASVS/Mobile Top 10, provides source-level navigation, and exports SARIF, CycloneDX SBOM, and PDF reports, with optional (non-scanning) AI assistance via Claude, OpenAI, Gemini, DeepSeek, or local Ollama for explaining findings.

AndroidiOSDocker+3

Mobile Security, AppSec· Published and added 31 Jul 2026

fossa.comarticle🛡️ Security

FOSSA: CISA Releases the 2026 SBOM Minimum Elements

FOSSA breaks down CISA's 2026 Minimum Elements for a Software Bill of Materials, the first major revision since NTIA's original 2021 baseline, produced with NSA, FBI, and 15 international agencies. The update roughly doubles required data fields, adding 10 new elements (SBOM Author Signature, SBOM Data Format Name/Version, Generation Context, Tool Name/Version, SBOM Version, Component Hash Value/Algorithm, and Component License) while renaming and clarifying existing fields (e.g., Supplier Name → Component Producer) and mandating full transitive-dependency coverage with no minimum depth, RFC 9557 timestamps, and dropping SWID in favor of SPDX/CycloneDX.

SBOMSPDXCycloneDX+1
CISANTIAExecutive Order 14028

Supply Chain, GRC· Published and added 31 Jul 2026

endorlabs.comarticle🛡️ Security

Best SBOM Tools in 2026, Compared | Blog | Endor Labs

Endor Labs' 2026 SBOM tooling comparison sorts five tools into three functional layers: open-source generators (Syft, cdxgen, Microsoft SBOM Tool) that produce SPDX/CycloneDX inventories, OWASP Dependency-Track for centralized SBOM storage and continuous monitoring, and Endor Labs' own SBOM Hub which adds function-level reachability analysis to cut CVE alert noise by a claimed 95%. It breaks down each tool's ecosystem coverage, format support, and trade-offs (e.g., Syft's lack of reachability, cdxgen's CycloneDX-only output, Dependency-Track's need for a database) and gives a decision framework for picking a tool by stack and maturity level.

Endor LabsSyftSBOM+3

Supply Chain· Added 3 Sep 2026, published 29 Jul 2026

wolfssl.comarticle🛡️ Security

wolfBoot 2.9.0

wolfSSL's release announcement for wolfBoot 2.9.0, an open-source secure bootloader for embedded systems, covering new hardware targets (STM32N6/U3/C5/G4/WBA, NXP LPC54S018M-EVK, Kinetis KL26, Xilinx Zynq-7000), new crypto features (RSA-PSS image signatures, hardware crypto-callback interface, multi-root-CA verification, pre-computed IDevID/DICE attestation), and continued security hardening from Fenrir fuzzing including bounded unauthenticated image sizes, memory-copy limits during updates, and fault-injection resistant integrity verification. It also adds an sbom Makefile target producing CycloneDX and SPDX output for CRA-readiness.

wolfBootwolfSSLwolfHSM+3
LMSXMSS

Hardware & RF· Published and added 25 Jul 2026

github.comrepo🛡️ Security

GoogleCloudPlatform/k8s-aibom

k8s-aibom is a Kubernetes controller from GoogleCloudPlatform that generates CycloneDX 1.6 ML-BOM documents at runtime for AI workloads — inference services (vLLM, TGI, Triton, Ollama), agent stacks (LangChain, AutoGen, CrewAI), RAG/vector DB infrastructure (Milvus, Qdrant, Weaviate), and training/eval jobs — by watching Kubernetes API objects with no privileged access. Each BOM attribute carries a declared/inferred/unresolved confidence flag and evidence locator, and the project positions its output as auditor-traceable evidence for EU AI Act Article 12/50, NIST AI RMF, and ISO/IEC 42001 compliance, with redaction filters, immutable GCS write-once sinks, and Sigstore-signed release attestations.

KubernetesCycloneDXSigstore+3
EU AI ActNIST AI RMFISO/IEC 42001+2

Supply Chain, Cloud & Infra, GRC· Published and added 18 Jul 2026

github.comrepo🛡️ Security

apisec-inc/AI-Surface

ai-surface is a local/offline static analysis CLI (apisec-inc) that scans a codebase for AI attack surface — LLM SDK calls, agent frameworks (LangChain, AWS Strands), MCP servers, RAG/vector stores, model gateways, and provider keys — and flags risk indicators such as financial-action tools with no human approval or unverified MCP servers. It generates an AI-BOM (CycloneDX), SARIF for GitHub code scanning, and maps findings to OWASP LLM Top 10, EU AI Act, NIST AI RMF, and ISO/IEC 42001, with a baseline+fail-on-severity workflow for gating new risk in PRs without blocking on pre-existing debt.

Model Context ProtocolLangChainPython+4
OWASP Top 10 for LLM ApplicationsEU AI ActNIST AI RMF+1

AI Security, DevSecOps· Published and added 11 Jul 2026

github.comrepo🛡️ Security

RAPTOR

RAPTOR is an autonomous offensive/defensive security research framework built on top of Claude Code that chains static analysis (Semgrep, Coccinelle, CodeQL), binary analysis (radare2, Frida, Z3-based exploit feasibility), LLM-driven multi-stage vulnerability validation, exploit PoC generation, and patch writing into a single workflow against source code or compiled binaries. It also includes an /sca supply-chain command that enriches dependency findings with OSV, CISA KEV, EPSS, and SSVC data and emits CycloneDX SBOMs, and sandboxes LLM-generated/untrusted code execution using Linux namespaces, Landlock, and seccomp. Authored by Gadi Evron, Daniel Cuthbert, Thomas Dullien (Halvar Flake), Michael Bargury, and John Cartwright, it ships 200+ custom static analysis rules and supports multi-model LLM analysis (Claude, GPT, Gemini, Ollama).

Claude CodeSemgrepCodeQL+5
Gadi EvronDaniel CuthbertThomas Dullien+2

AppSec, Offensive Security, AI Security, Supply Chain· Published and added 28 Jun 2026

fossa.comarticle🛡️ Security

FOSSA: Allan Friedman

Allan Friedman, former NTIA/CISA SBOM and VEX program lead, lays out practical VEX workflows for both software producers and consumers: tracking exposure via SBOM plus CVE/OSV feeds, doing reachability-based impact analysis, documenting and publishing determinations, and closing the loop as status changes. He compares the four VEX formats (CSAF, CycloneDX, SPDX 3.0, OpenVEX), ranks the five standard "not affected" justifications by how verifiable/trustworthy they are, and ties adoption to emerging regulatory pressure from the EU Cyber Resilience Act and FDA medical-device SBOM review.

SBOMCycloneDXSPDX+3
Allan FriedmanNTIACISA+4

Supply Chain, GRC· Published and added 27 Jun 2026

aikido.devarticle🛡️ Security

SBOMs in 2026: Everyone's generating them, no one's using them

Aikido Security's blog post recaps ENISA's SBOM Adoption State of Play 2026 report, a survey of 334 organizations (65% EU-based, 80% impacted by the Cyber Resilience Act). Key findings: most orgs now generate SBOMs at build time but rarely consume them for security (only 7% have closed the generation-to-usage gap), 39% never receive SBOMs from suppliers, 28% still use proprietary/non-standard formats instead of CycloneDX (44%) or SPDX (29%), and coverage of transitive dependencies remains weak even though most real-world vulnerabilities hide there. The piece then pitches Aikido's Syft-based SBOM generation, CycloneDX/SPDX export, supplier SBOM import, and Device Protection as ways to close these gaps ahead of the CRA's December 2027 deadline.

SBOMCycloneDXSPDX+2
ENISABSIEU Cyber Resilience Act

Supply Chain, GRC· Added 3 Sep 2026, published 10 Jun 2026

github.comrepo🛡️ Security

CVE Lite CLI

CVE Lite CLI is an OWASP Lab Project CLI that scans npm, pnpm, Yarn, and Bun lockfiles against OSV and the npm advisory API and outputs copy-and-run fix commands instead of raw CVE lists, with parent-aware guidance for transitive dependencies. Beyond core CVE scanning it audits override/resolution hygiene, flags maintenance risk (deprecated direct deps and version drag blocking fixes), warns when a suggested fix falls inside a package manager's release-cooldown window (referencing the chalk/debug npm compromise), and emits SARIF, SPDX/CycloneDX SBOMs, and EPSS-based priority tiers, plus a GitHub Action that opens batched fix PRs.

npmpnpmYarn+3
chalk

Supply Chain, DevSecOps· Published and added 31 May 2026

github.comrepo🛡️ Security

FoxGuard

FoxGuard is a fast local/CI security scanner offering 200+ built-in rules across 12 languages, cross-file taint tracking for 14 languages, secrets scanning, OSV-backed dependency (SCA) scanning, and a post-quantum crypto (PQC) audit that flags quantum-vulnerable primitives (RSA, ECDSA/DSA, ECDH/DH) against CNSA 2.0 deadlines while also inventorying already-adopted PQC algorithms (ML-KEM, ML-DSA, SLH-DSA, FN-DSA, HQC). It ships a Semgrep/OpenGrep-compatible YAML rule bridge covering ~98% of the public Semgrep registry, outputs to SARIF/CycloneDX 1.6 CBOM/Semgrep-JSON, and integrates via GitHub Action, pre-commit, VS Code, Claude Code plugin, and MCP server, plus an interactive TUI for reviewing findings and baselines. It's part of the "0sec" open cybersecurity harness project.

SemgrepOpengrepSARIF+5
0secCNSA 2.0

AppSec, DevSecOps, Supply Chain· Added 3 Sep 2026, published 16 May 2026

github.comrepo🛡️ Security

OWASP/DockSec

DockSec is an OWASP Lab Project CLI that wraps Trivy, Hadolint, and Docker Scout to scan Dockerfiles, images, and Compose files, then uses an AI provider (OpenAI, Anthropic, Google, or local Ollama) to correlate findings, cut noise, and generate plain-English remediation suggestions. It supports CI/CD gating via exit codes, baselines, and auditable waiver files, outputs SARIF/CycloneDX SBOM/HTML/PDF/JSON/CSV/Markdown reports, and redacts secrets before any content reaches an LLM, with a fully offline/local-only mode for air-gapped teams.

DockerTrivyHadolint+3
CVE-2023-45853

DevSecOps· Published and added 14 May 2026

socket.devarticle🛡️ Security

Socket: pnpm 11 Adds Supply Chain Protection Defaults

Socket covers pnpm 11's new security-by-default settings: a 24-hour Minimum Release Age that delays resolution of freshly published package versions, blockExoticSubdeps which by default rejects transitive dependencies resolved from git/tarball URLs instead of the registry, and a new allowBuilds model that consolidates prior build-script controls (onlyBuiltDependencies, ignoreDepScripts, etc.) into a single package-pattern-to-boolean map. The piece ties these defaults to the conditions exploited by the Mini Shai-Hulud campaign (npm/PyPI/Packagist compromise using preinstall hooks to fetch a Bun runtime and run a credential stealer), and also notes pnpm 11's built-in SBOM generation (CycloneDX 1.7/SPDX 2.3), GHSA-based audit --fix=update, and a preview of the Rust-based Pacquet install engine slated for pnpm v12.

pnpmnpmCycloneDX+3
Mini Shai-HuludPacquet

Supply Chain· Published and added 7 May 2026

github.comrepo🛡️ Security

CRA Compliance Lab

CRA Compliance Lab is a GitHub organization hosting tooling and curated resources for EU Cyber Resilience Act (Regulation 2024/2847) compliance, including cra-sbom-cli — a local CLI that pre-flights CycloneDX or SPDX SBOM files against CRA-aligned content checks and outputs a PDF report — plus an awesome-list covering the regulation, harmonised standards, EUCC, and vulnerability management, and forks of sbomqs and the ENISA Secure by Design/Default playbook. It matters as one of the few practical, hands-on toolsets for organizations operationalizing CRA SBOM and secure-by-design requirements rather than just discussing the law.

CycloneDXSPDXPython+1
EU Cyber Resilience ActENISA

GRC, Supply Chain· Published and added 6 May 2026

Showing 30 of 31

Show more