Skip to content

Security Deep Dive

girste/mcp-cybersec-watchdog

Security posture and CVE patch evidence from tracked releases.

Back to Tool

No CVEs tracked against v0.2Teacup.

— Signed — SLSA — SBOM ✓ Security policy Unknown cadence Sporadic maintainer

Trust Signals — 2 of 9 Present

Evidence already collected from releases and repository metadata.

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

0.74 / 1.0

116d stale

scorecard

2.64 / 4.0

Score 6.6/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.6

40%

scorecard score: 6.6 openssf badge: none

Maintainer health

maintainer health

7.4

10%

activity freshness: 116d

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.6/10

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

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

Beta — feedback welcome: [email protected]