Skip to content
Tools / Openmeetings / Security

Security Deep Dive

Openmeetings

Security posture and CVE patch evidence from tracked releases.

Back to Tool

No CVEs tracked against 8.1.0.

— Signed — SLSA — SBOM ✗ Security policy Unknown cadence Active maintainer

Trust Signals — 1 of 9 Present

Evidence already collected from releases and repository metadata.

1/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: 18d ago
Release cadence Unknown
12-release median Release history
Latest release: 8mo ago
Maintainer active Present
Recent commit activity Repository
Last commit: 2d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 8mo ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 8mo ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 8mo ago
7.7/10 Security Score
4.8/10 Scorecard

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

2d stale

scorecard

1.92 / 4.0

Score 4.8/10

cve health

2.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

0.00 / 10.0

Risk 0.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

10.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

10.0

10%

supply chain risk: 0.0 transitive cves: 0c/0h

Provenance trust

provenance trust

4.8

40%

scorecard score: 4.8 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 2d

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.

Scorecard

Scorecard 4.8/10

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

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

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Beta — feedback welcome: [email protected]