Skip to content

Security Deep Dive

iris-eval/mcp-server

Security posture and CVE patch evidence from tracked releases.

Back to Tool

No CVEs tracked against v0.4.3.

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

Trust Signals — 4 of 9 Present

Evidence already collected from releases and repository metadata.

4/9 Present
Signed releases Present
Latest release artifact signature Sigstore
Last verified: 8d ago
SLSA provenance Absent
Attestation predicate level Latest release
Last verified: 8d ago
SBOM published Unknown
GitHub SBOM API Latest release
SECURITY.md Present
GitHub repository metadata Repository policy
Checked: 19d ago
Release cadence: weekly Present
2d median over recent releases Release history
Latest release: 13d ago
Maintainer active Present
Recent commit activity Repository
Last commit: 9d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 13d ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 13d ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 13d ago
7.2/10 Security Score
6.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

9d stale

scorecard

2.72 / 4.0

Score 6.8/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

6.8

40%

scorecard score: 6.8 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 9d

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

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

Check Score Reason
Code-Review 0 Found 0/12 approved changesets -- score normalized to 0
Dependency-Update-Tool 10 update tool detected
Maintained 0 project was created within the last 90 days. Please review its contents carefully
Dangerous-Workflow 10 no dangerous workflow patterns detected
Security-Policy 10 security policy file detected
Binary-Artifacts 10 no binaries found in the repo
Token-Permissions 10 GitHub workflow tokens follow principle of least privilege
Pinned-Dependencies 6 dependency not pinned by hash detected -- score normalized to 6
License 10 license file detected
CII-Best-Practices 5 badge detected: Passing
Packaging 10 packaging workflow detected
Vulnerabilities 7 3 existing vulnerabilities detected
SAST 10 SAST tool is run on all commits
Fuzzing 0 project is not fuzzed
Branch-Protection 8 branch protection is not maximal on development and all release branches
Signed-Releases 3 2 out of the last 5 releases have a total of 2 signed artifacts.
Contributors 3 project has 1 contributing companies or organizations -- score normalized to 3
CI-Tests 10 30 out of 30 merged PRs checked by a CI test -- score normalized to 10

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Beta — feedback welcome: [email protected]