Skip to content
Tools / revealjs / Security

Security Deep Dive

revealjs

Security posture and CVE patch evidence from tracked releases.

Back to Tool

No CVEs tracked against 6.0.1.

✗ 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 Absent
Latest release artifact signature None
Last verified: 9d ago
SLSA provenance Absent
Attestation predicate level Latest release
Last verified: 9d ago
SBOM published Unknown
GitHub SBOM API Latest release
SECURITY.md Absent
GitHub repository metadata Repository policy
Checked: 17d ago
Release cadence Unknown
12-release median Release history
Latest release: 1mo ago
Maintainer active Present
Recent commit activity Repository
Last commit: 13d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 1mo ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 1mo ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 1mo ago
6.7/10 Security Score
5.4/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

13d stale

scorecard

2.16 / 4.0

Score 5.4/10

cve health

1.25 / 2.5

⚠ Estimated — no scan yet

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

5.0

25%

direct cves: clear cve scan: estimated

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

5.4

40%

scorecard score: 5.4 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 13d

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 5.4/10

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

Check Score Reason
Code-Review 0 Found 1/29 approved changesets -- score normalized to 0
Packaging -1 packaging workflow not detected
Dangerous-Workflow 10 no dangerous workflow patterns detected
Maintained 10 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions 10 GitHub workflow tokens follow principle of least privilege
Binary-Artifacts 10 no binaries found in the repo
CII-Best-Practices 0 no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies 0 dependency not pinned by hash detected -- score normalized to 0
Security-Policy 0 security policy file not detected
License 10 license file detected
Fuzzing 0 project is not fuzzed
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
SAST 0 SAST tool is not run on all commits -- score normalized to 0
Signed-Releases -1 no releases found

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Beta — feedback welcome: [email protected]