Tools / MediKeep / Security

Security Deep Dive

MediKeep

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 critical dependency CVE affects v0.67.0.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA — SBOM ✗ Security policy Weekly cadence · 4d 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: 22d ago

Release cadence: weekly Present

4d median over recent releases Release history

Latest release: 1d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 1d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 1d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 1d ago

Signing assets Not active yet

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

Latest release: 1d ago

3.8/10 Security Score

Dependency Exposure 54 transitive dependency CVEs found in the latest SBOM. 1 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.00 / 4.0

⚠ Estimated — not yet collected

cve health

0.00 / 2.5

⚠ No direct scan — 1c/26h transitive 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 57.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

4.3

10%

supply chain risk: 56.97 transitive cves: 1c/26h

Provenance trust

provenance trust

5.0

40%

scorecard score: estimated 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 57.0/100

1 Transitive critical CVEs

0 KEV-transitive CVEs

52% Dependency freshness

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

1023 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 (8) All (54)

Critical 1 High 26 Medium 25 Low 2

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2019-6446	critical	—	numpy	—	v0.66.0
CVE-2014-1858	high	—	numpy	—	v0.66.0
CVE-2014-1859	high	—	numpy	—	v0.66.0
CVE-2017-12852	high	—	numpy	—	v0.66.0
CVE-2021-39229	high	—	apprise	—	v0.66.0
CVE-2021-41495	high	—	numpy	—	v0.66.0
CVE-2024-23342	high	—	ecdsa	0.19.2	v0.66.0
CVE-2026-22029	high	—	@remix-run/router	1.23.0	v0.66.0
CVE-2026-26996	high	—	minimatch	3.1.2	v0.66.0
CVE-2026-27606	high	—	rollup	2.79.2	v0.66.0
CVE-2026-27903	high	—	minimatch	3.1.2	v0.66.0
CVE-2026-27904	high	—	minimatch	3.1.2	v0.66.0
CVE-2026-32141	high	—	flatted	3.3.3	v0.66.0
CVE-2026-33228	high	—	flatted	3.3.3	v0.66.0
CVE-2026-33671	high	—	picomatch	4.0.3	v0.66.0
CVE-2026-34601	high	—	@xmldom/xmldom	0.8.11	v0.66.0
CVE-2026-39363	high	—	vite	7.3.1	v0.66.0
CVE-2026-39364	high	—	vite	7.3.1	v0.66.0
CVE-2026-41672	high	—	@xmldom/xmldom	0.8.11	v0.66.0
CVE-2026-41673	high	—	@xmldom/xmldom	0.8.11	v0.66.0
CVE-2026-41674	high	—	@xmldom/xmldom	0.8.11	v0.66.0
CVE-2026-41675	high	—	@xmldom/xmldom	0.8.11	v0.66.0
CVE-2026-42033	high	—	axios	1.14.0	v0.66.0
CVE-2026-42035	high	—	axios	1.14.0	v0.66.0
CVE-2026-42043	high	—	axios	1.14.0	v0.66.0
CVE-2026-42264	high	—	axios	1.14.0	v0.66.0
CVE-2026-4800	high	—	lodash	4.17.23	v0.66.0
CVE-2021-33430	medium	—	numpy	—	v0.66.0
CVE-2021-34141	medium	—	numpy	—	v0.66.0
CVE-2021-41496	medium	—	numpy	—	v0.66.0
CVE-2025-62718	medium	—	axios	1.14.0	v0.66.0
CVE-2025-64718	medium	—	js-yaml	4.1.0	v0.66.0
CVE-2025-68470	medium	—	react-router	6.30.1	v0.66.0
CVE-2025-69873	medium	—	ajv	6.12.6	v0.66.0
CVE-2026-2950	medium	—	lodash	4.17.23	v0.66.0
CVE-2026-33672	medium	—	picomatch	4.0.3	v0.66.0
CVE-2026-33750	medium	—	brace-expansion	1.1.12	v0.66.0
CVE-2026-39365	medium	—	vite	7.3.1	v0.66.0
CVE-2026-40175	medium	—	axios	1.14.0	v0.66.0
CVE-2026-40186	medium	—	sanitize-html	2.17.2	v0.66.0
CVE-2026-41305	medium	—	postcss	8.5.6	v0.66.0
CVE-2026-41691	medium	—	i18next-http-backend	3.0.2	v0.66.0
CVE-2026-42034	medium	—	axios	1.14.0	v0.66.0
CVE-2026-42036	medium	—	axios	1.14.0	v0.66.0
CVE-2026-42037	medium	—	axios	1.14.0	v0.66.0
CVE-2026-42038	medium	—	axios	1.14.0	v0.66.0
CVE-2026-42039	medium	—	axios	1.14.0	v0.66.0
CVE-2026-42041	medium	—	axios	1.14.0	v0.66.0
CVE-2026-42042	medium	—	axios	1.14.0	v0.66.0
CVE-2026-42044	medium	—	axios	1.14.0	v0.66.0
GHSA-67mh-4wv8-2f99	medium	—	esbuild	0.23.1	v0.66.0
GHSA-r4q5-vmmm-2653	medium	—	follow-redirects	1.15.11	v0.66.0
CVE-2024-47764	low	—	cookie	0.4.2	v0.66.0
CVE-2026-42040	low	—	axios	1.14.0	v0.66.0

Showing 54 of 54