Tools / kinto / Security

Security Deep Dive

kinto

Security posture and CVE patch evidence from tracked releases.

Back to Tool

2 critical dependency CVEs affects 26.2.0.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA — SBOM ✓ Security policy Weekly cadence · 7d median Active maintainer

Trust Signals — 3 of 9 Present

Evidence already collected from releases and repository metadata.

3/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 Present

GitHub repository metadata Repository policy

Checked: 22d ago

Release cadence: weekly Present

7d median over recent releases Release history

Latest release: 5d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 1d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 5d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 5d ago

Signing assets Not active yet

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

Latest release: 5d ago

5.0/10 Security Score

6.9/10 Scorecard

Dependency Exposure 28 transitive dependency CVEs found in the latest SBOM. 2 critical.

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

2.76 / 4.0

Score 6.9/10

cve health

0.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 24.5/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

2.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

7.6

10%

supply chain risk: 24.47 transitive cves: 2c/8h

Provenance trust

provenance trust

6.9

40%

scorecard score: 6.9 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 24.5/100

2 Transitive critical CVEs

0 KEV-transitive CVEs

76% Dependency freshness

Scorecard

Scorecard 6.9/10

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

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

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

237 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 (25) All (28)

Critical 2 High 8 Medium 16 Low 2

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2024-49768	critical	—	waitress	2.1.2	26.1.1
CVE-2025-43859	critical	—	h11	0.14.0	26.1.1
CVE-2023-28117	high	—	sentry-sdk	—	26.1.1
CVE-2023-48052	high	—	httpie	3.2.4	26.1.1
CVE-2023-5590	high	—	selenium	4.12.0	26.1.1
CVE-2024-34069	high	—	werkzeug	3.0.1	26.1.1
CVE-2024-49769	high	—	waitress	2.1.2	26.1.1
CVE-2025-66418	high	—	urllib3	2.1.0	26.1.1
CVE-2025-66471	high	—	urllib3	2.1.0	26.1.1
CVE-2026-21441	high	—	urllib3	2.1.0	26.1.1
CVE-2024-35195	medium	—	requests	2.31.0	26.1.1
CVE-2024-3651	medium	—	idna	3.6	26.1.1
CVE-2024-37891	medium	—	urllib3	2.1.0	26.1.1
CVE-2024-42353	medium	—	webob	1.8.7	26.1.1
CVE-2024-47081	medium	—	requests	2.31.0	26.1.1
CVE-2024-49766	medium	—	werkzeug	3.0.1	26.1.1
CVE-2024-49767	medium	—	werkzeug	3.0.1	26.1.1
CVE-2024-5569	medium	—	zipp	3.17.0	26.1.1
CVE-2025-50181	medium	—	urllib3	2.1.0	26.1.1
CVE-2025-66221	medium	—	werkzeug	3.0.1	26.1.1
CVE-2025-71176	medium	—	pytest	7.4.4	26.1.1
CVE-2026-21860	medium	—	werkzeug	3.0.1	26.1.1
CVE-2026-25645	medium	—	requests	2.31.0	26.1.1
CVE-2026-27199	medium	—	werkzeug	3.0.1	26.1.1
CVE-2026-3219	medium	—	pip	26.0.1	26.1.1
CVE-2026-6357	medium	—	pip	26.0.1	26.1.1
CVE-2024-39689	low	—	certifi	2023.11.17	26.1.1
CVE-2024-40647	low	—	sentry-sdk	—	26.1.1

Showing 28 of 28