Tools / convoy / Security

Security Deep Dive

convoy

Security posture and CVE patch evidence from tracked releases.

Back to Tool

14 high-severity dependency CVEs affects v26.6.8.

Review the dependency vulnerabilities below.

— Signed — SLSA — SBOM ✗ Security policy Weekly cadence · 3d median Active maintainer

Trust Signals — 2 of 9 Present

Evidence already collected from releases and repository metadata.

2/9 Present

Signed releases Unknown

Latest release artifact signature Latest release

—

SLSA provenance Unknown

Attestation predicate level Latest release

—

SBOM published Unknown

GitHub SBOM API Latest release

—

SECURITY.md Absent

GitHub repository metadata Repository policy

Checked: 14d ago

Release cadence: weekly Present

3d median over recent releases Release history

Latest release: 2d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 9d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 2d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 2d ago

Signing assets Not active yet

.sig, .crt, cosign.pub, or similar Release asset

Latest release: 2d ago

5.2/10 Security Score

4.8/10 Scorecard

Dependency Exposure 32 transitive dependency CVEs found in the latest SBOM.

Security Score

A composite score aggregating Scorecard performance, CVE patch history, OpenSSF badge tier, and dependency vulnerability exposure. Score ≥ 7.0 is healthy; < 4.0 warrants attention.

epss

0.25 / 0.5

No EPSS data

freshness

1.00 / 1.0

1d stale

scorecard

1.92 / 4.0

Score 4.8/10

cve health

1.50 / 2.5

No open CVEs

patch speed

0.50 / 0.5

⚠ Estimated — no CVE patch history

kev exposure

1.50 / 1.5

No KEV exposure

supply chain risk

-1.50 / 10.0

Risk 28.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

6.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

7.2

10%

supply chain risk: 28.01 transitive cves: 0c/14h

Provenance trust

provenance trust

4.8

40%

scorecard score: 4.8 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 1d

Operational risk

operational risk

8.5

10%

kev exposure: clear epss max: none

How is this calculated?

The six dimensions group the legacy score signals into weighted categories: direct vulnerability status, patch responsiveness, dependency exposure, provenance checks, maintainer activity, and exploitability risk. The flat component values above remain available for compatibility.

Supply Chain Risk

Risk 28.0/100

0 Transitive critical CVEs

0 KEV-transitive CVEs

100% Dependency freshness

Scorecard

Scorecard 4.8/10

OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.

Check	Score	Reason
Code-Review	1	Found 3/30 approved changesets -- score normalized to 1
Maintained	10	30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices	0	no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow	0	dangerous workflow patterns detected
Security-Policy	0	security policy file not detected
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
Binary-Artifacts	10	no binaries found in the repo
License	9	license file detected
Fuzzing	0	project is not fuzzed
Signed-Releases	-1	no releases found
Branch-Protection	8	branch protection is not maximal on development and all release branches
Pinned-Dependencies	7	dependency not pinned by hash detected -- score normalized to 7
Packaging	10	packaging workflow detected
SAST	10	SAST tool is run on all commits

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

324 dependencies scanned View full dependency list →

Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.

Critical

High

Medium

Low

Unknown

Still affecting latest (3) All (32)

High 14 Medium 14 Low 1 Unknown 3

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2024-39338	high	—	axios	1.6.7	v26.6.0
CVE-2025-27152	high	—	axios	1.6.7	v26.6.0
CVE-2025-58754	high	—	axios	1.6.7	v26.6.0
CVE-2025-66035	high	—	@angular/common	14.0.3	v26.6.0
CVE-2025-66412	high	—	@angular/compiler	14.0.3	v26.6.0
CVE-2026-22610	high	—	@angular/core	14.0.3	v26.6.0
CVE-2026-22610	high	—	@angular/compiler	14.0.3	v26.6.0
CVE-2026-25639	high	—	axios	1.6.7	v26.6.0
CVE-2026-27970	high	—	@angular/core	14.0.3	v26.6.0
CVE-2026-34040	high	—	github.com/docker/docker	v28.5.2+incompatible	v26.6.0
CVE-2026-42033	high	—	axios	1.6.7	v26.6.0
CVE-2026-42035	high	—	axios	1.6.7	v26.6.0
CVE-2026-42043	high	—	axios	1.6.7	v26.6.0
CVE-2026-42264	high	—	axios	1.6.7	v26.6.0
CVE-2023-44270	medium	—	postcss	8.4.14	v26.6.0
CVE-2024-53382	medium	—	prismjs	1.29.0	v26.6.0
CVE-2025-62718	medium	—	axios	1.6.7	v26.6.0
CVE-2026-33997	medium	—	github.com/docker/docker	v28.5.2+incompatible	v26.6.0
CVE-2026-40175	medium	—	axios	1.6.7	v26.6.0
CVE-2026-41305	medium	—	postcss	8.4.14	v26.6.0
CVE-2026-42034	medium	—	axios	1.6.7	v26.6.0
CVE-2026-42036	medium	—	axios	1.6.7	v26.6.0
CVE-2026-42037	medium	—	axios	1.6.7	v26.6.0
CVE-2026-42038	medium	—	axios	1.6.7	v26.6.0
CVE-2026-42039	medium	—	axios	1.6.7	v26.6.0
CVE-2026-42041	medium	—	axios	1.6.7	v26.6.0
CVE-2026-42042	medium	—	axios	1.6.7	v26.6.0
CVE-2026-42044	medium	—	axios	1.6.7	v26.6.0
CVE-2026-42040	low	—	axios	1.6.7	v26.6.0
CVE-2020-8911	unknown	—	github.com/aws/aws-sdk-go	v1.55.6	v26.6.0
CVE-2020-8912	unknown	—	github.com/aws/aws-sdk-go	v1.55.6	v26.6.0
CVE-2026-33814	unknown	—	golang.org/x/net	v0.52.0	v26.6.0

Showing 32 of 32