ArtefactFlow
banner
artefactflow.com
ArtefactFlow
@artefactflow.com
Artefact & SBOM management for software teams. One source of truth: what's in every release, is it vulnerable, and where is it deployed?
Your pipeline knows what it built and where it deployed it. By the next run, most of that is gone.

ArtefactFlow keeps it: versions with their provenance, SBOM releases, and deployments Argo CD reads back.
www.artefactflow.com/solutions/pl...
#DevOps #DevSecOps
ArtefactFlow in your pipeline | ArtefactFlow
For platform and DevOps engineers: service accounts, GitHub Actions and GitLab CI, policies as release gates, signed SBOMs and the Argo CD generator.
www.artefactflow.com
November 21, 2026 at 8:33 AM
A false positive means the CVE was never in that component. "Not affected" means it is in a component you ship, but cannot be exploited here.

VEX makes you say which, with a coded reason:
www.artefactflow.com/blog/vex-exp...
#AppSec #VulnerabilityManagement
VEX explained: not every vulnerability applies to you | ArtefactFlow
A scanner flags 200 vulnerabilities in your release. Most of them don't actually affect you. VEX is how you say so, credibly and at scale. Here's how it works.
www.artefactflow.com
November 19, 2026 at 1:41 PM
What exactly is running in production right now, and can you prove it?

Most teams need twenty minutes and three tools to answer, and still are not sure. That gap is why we built ArtefactFlow.
www.artefactflow.com/blog/introdu...
#SBOM #DevOps
Why we built ArtefactFlow | ArtefactFlow
Most teams can't answer one simple question with confidence: what exactly is running in production right now? Here's why that has to change, and what we're doing about it.
www.artefactflow.com
November 17, 2026 at 8:01 AM
A critical CVE is published. Within minutes: are we using it, in which versions, where do they run, who owns them?

Across five tools, that is a fire drill. Our page for teams that run their own software:
www.artefactflow.com/solutions/so...
#DevSecOps #VulnerabilityManagement
Know what you ship, and where it runs | ArtefactFlow
For teams that build and run their own software: how ArtefactFlow turns the questions a new CVE raises into a lookup, from the artefact and its SBOM to every environment it runs in.
www.artefactflow.com
November 14, 2026 at 12:34 PM
Release notes describe intent. A diff of two SBOM versions shows what shipped: components added, removed or changed, and how the dependency graph moved.

One API call:
docs.artefactflow.com/guides/sbom-...
#SBOM #DevSecOps
Comparing SBOM versions
Diff two versions of the same SBOM to see which components were added, removed or changed, how the dependency graph moved, and which services came and went.
docs.artefactflow.com
November 12, 2026 at 10:20 AM
A scanner flags 200 vulnerabilities in your release. Most of them do not actually affect you.

VEX is how you say so, credibly and at scale, in a form your customer's tooling can read:
www.artefactflow.com/blog/vex-exp...
#AppSec #SBOM #VulnerabilityManagement
VEX explained: not every vulnerability applies to you | ArtefactFlow
A scanner flags 200 vulnerabilities in your release. Most of them don't actually affect you. VEX is how you say so, credibly and at scale. Here's how it works.
www.artefactflow.com
November 10, 2026 at 7:47 AM
Three questions reach every security leader: are we affected, can we prove it, and are we ready for the Cyber Resilience Act?

Our page for CISOs and CTOs, with a one-pager for your next meeting:
www.artefactflow.com/solutions/se...
#AppSec #CyberResilienceAct
Software risk you can answer for | ArtefactFlow
For CISOs, CTOs and heads of compliance: how ArtefactFlow answers "are we affected?", "can we prove it?" and "are we ready for the Cyber Resilience Act?" with evidence you can show.
www.artefactflow.com
November 7, 2026 at 1:44 PM
Reposted by ArtefactFlow
If you are part of a #technologyalliance that creates, uses, or manages open source software, do you know how the EU #CyberResilienceAct affects you – e.g., what are your reporting requirements, if any? Read below to find out more:

www.openlogic.com/blog/cyber-r...
How the Cyber Resilience Act Impacts Organizations Running Open Source Software | OpenLogic
An overview of the EU's Cyber Resilience Act, who it impacts, and how to meet CRA compliance requirements for open source software in your stack.
www.openlogic.com
November 4, 2026 at 5:44 PM
Somebody hands you a signed SBOM. Can you check it without an account at the vendor that signed it?

Yes: verify the DSSE envelope offline against the organisation's public JWKS. No account, no call to us.
docs.artefactflow.com/guides/verif...
#SBOM #SupplyChainSecurity
Verifying signed SBOMs
Check an SBOM version's signature through the API, or verify its DSSE envelope offline against the organisation's public JWKS with no ArtefactFlow account at all.
docs.artefactflow.com
November 5, 2026 at 5:44 PM
An auditor asks: can you prove this record is complete, and that nobody edited it?

The audit archive is write-once and hash-chained, and every page you export comes with proof attached.
docs.artefactflow.com/guides/audit...
#Compliance #DevSecOps
Exporting the audit archive
Export your organisation's complete audit history over the API, with cryptographic proof that nothing has been altered or dropped.
docs.artefactflow.com
November 3, 2026 at 8:03 PM
A practical, jargon-light tour of what a CycloneDX Software Bill of Materials contains (components, dependencies, metadata and signatures) and why each part matters. Do reed our blog at artefactflow.com/blog/what-go... #sbom #cyclonedx #billofmaterials
What actually goes in a CycloneDX 1.7 SBOM | ArtefactFlow
A practical, jargon-light tour of what a CycloneDX Software Bill of Materials contains (components, dependencies, metadata and signatures) and why each part matters.
artefactflow.com
October 29, 2026 at 11:33 AM