Tools / openproject / Security

Security Deep Dive

openproject

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 critical dependency CVE affects v17.4.0.

Audit transitive dependencies; consider upgrading or pinning replacements.

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

Trust Signals — 3 of 9 Present

Evidence already collected from releases and repository metadata.

3/9 Present

Signed releases Absent

Latest release artifact signature None

Last verified: 15d ago

SLSA provenance Absent

Attestation predicate level Latest release

Last verified: 15d ago

SBOM published Unknown

GitHub SBOM API Latest release

—

SECURITY.md Present

GitHub repository metadata Repository policy

Checked: 22d ago

Release cadence: weekly Present

0d median over recent releases Release history

Latest release: 21d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 1d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 21d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 21d ago

Signing assets Not active yet

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

Latest release: 21d ago

4.6/10 Security Score

7.1/10 Scorecard

Dependency Exposure 23 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.84 / 4.0

Score 7.1/10

cve health

0.00 / 2.5

⚠ No direct scan — 1c/9h 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 22.6/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

7.7

10%

supply chain risk: 22.61 transitive cves: 1c/9h

Provenance trust

provenance trust

7.1

40%

scorecard score: 7.1 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 22.6/100

1 Transitive critical CVEs

0 KEV-transitive CVEs

70% Dependency freshness

Scorecard

Scorecard 7.1/10

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

Check	Score	Reason
Code-Review	6	Found 11/18 approved changesets -- score normalized to 6
Maintained	10	30 commit(s) and 0 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
Security-Policy	9	security policy file detected
Dangerous-Workflow	10	no dangerous workflow patterns detected
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
License	10	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
Fuzzing	0	project is not fuzzed
Signed-Releases	-1	no releases found
Binary-Artifacts	10	no binaries found in the repo
Packaging	10	packaging workflow detected
SAST	10	SAST tool is run on all commits
Pinned-Dependencies	6	dependency not pinned by hash detected -- score normalized to 6

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

2965 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 (23) All (23)

Critical 1 High 9 Medium 10 Low 3

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2026-41242	critical	—	protobufjs	7.5.4	v17.2.4
CVE-2026-26996	high	—	minimatch	5.1.6	v17.2.4
CVE-2026-27903	high	—	minimatch	5.1.6	v17.2.4
CVE-2026-27904	high	—	minimatch	5.1.6	v17.2.4
CVE-2026-33036	high	—	fast-xml-parser	5.3.6	v17.2.4
CVE-2026-33151	high	—	socket.io-parser	4.2.4	v17.2.4
CVE-2026-33671	high	—	picomatch	4.0.3	v17.2.4
CVE-2026-44728	high	—	@babel/plugin-transform-modules-systemjs	7.29.0	v17.2.4
CVE-2026-6321	high	—	fast-uri	3.1.0	v17.2.4
CVE-2026-6322	high	—	fast-uri	3.1.0	v17.2.4
CVE-2025-69873	medium	—	ajv	6.12.6	v17.2.4
CVE-2026-33349	medium	—	fast-xml-parser	5.3.6	v17.2.4
CVE-2026-33532	medium	—	yaml	1.10.2	v17.2.4
CVE-2026-33672	medium	—	picomatch	4.0.3	v17.2.4
CVE-2026-33750	medium	—	brace-expansion	2.0.2	v17.2.4
CVE-2026-41305	medium	—	postcss	8.5.6	v17.2.4
CVE-2026-41650	medium	—	fast-xml-parser	5.3.6	v17.2.4
CVE-2026-42338	medium	—	ip-address	10.1.0	v17.2.4
CVE-2026-44455	medium	—	hono	4.12.14	v17.2.4
CVE-2026-44456	medium	—	hono	4.12.14	v17.2.4
CVE-2025-66803	low	—	@hotwired/turbo	8.0.20	v17.2.4
CVE-2026-24001	low	—	diff	4.0.2	v17.2.4
CVE-2026-27942	low	—	fast-xml-parser	5.3.6	v17.2.4

Showing 23 of 23