Tools / countly-server / Security

Security Deep Dive

countly-server

Security posture and CVE patch evidence from tracked releases.

Back to Tool

12 high-severity dependency CVEs affects 25.03.45.

Review the dependency vulnerabilities below.

— 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: 7d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 1d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 7d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 7d ago

Signing assets Not active yet

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

Latest release: 7d ago

4.8/10 Security Score

7.0/10 Scorecard

Dependency Exposure 18 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

Up to date

scorecard

2.80 / 4.0

Score 7.0/10

cve health

0.25 / 2.5

⚠ No direct scan — 0c/12h 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 24.9/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

1.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

7.5

10%

supply chain risk: 24.89 transitive cves: 0c/12h

Provenance trust

provenance trust

7.0

40%

scorecard score: 7.0 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 0d

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.9/100

0 Transitive critical CVEs

0 KEV-transitive CVEs

56% Dependency freshness

Scorecard

Scorecard 7.0/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
Maintained	10	30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Security-Policy	10	security policy file detected
CII-Best-Practices	0	no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow	10	no dangerous workflow patterns detected
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
License	9	license file detected
Branch-Protection	-1	internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Signed-Releases	-1	no releases found
Packaging	10	packaging workflow detected
SAST	10	SAST tool is run on all commits
Fuzzing	0	project is not fuzzed
Binary-Artifacts	9	binaries present in source code
Pinned-Dependencies	0	dependency not pinned by hash detected -- score normalized to 0

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

1677 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 (18) All (18)

High 12 Medium 4 Low 2

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2026-23745	high	—	tar	6.2.1	24.05.50
CVE-2026-23950	high	—	tar	6.2.1	24.05.50
CVE-2026-24842	high	—	tar	6.2.1	24.05.50
CVE-2026-26960	high	—	tar	6.2.1	24.05.50
CVE-2026-26996	high	—	minimatch	3.0.8	24.05.50
CVE-2026-27903	high	—	minimatch	3.0.8	24.05.50
CVE-2026-27904	high	—	minimatch	3.0.8	24.05.50
CVE-2026-29786	high	—	tar	6.2.1	24.05.50
CVE-2026-31802	high	—	tar	6.2.1	24.05.50
CVE-2026-44240	high	—	basic-ftp	5.3.0	24.05.50
CVE-2026-44665	high	—	fast-xml-builder	1.1.5	24.05.50
GHSA-5c6j-r48x-rmvq	high	—	serialize-javascript	6.0.2	24.05.50
CVE-2026-33750	medium	—	brace-expansion	2.0.2	24.05.50
CVE-2026-34043	medium	—	serialize-javascript	6.0.2	24.05.50
CVE-2026-42338	medium	—	ip-address	10.1.0	24.05.50
CVE-2026-44664	medium	—	fast-xml-builder	1.1.5	24.05.50
CVE-2026-24001	low	—	diff	7.0.0	24.05.50
CVE-2026-3449	low	—	@tootallnate/once	1.1.2	24.05.50

Showing 18 of 18