Skip to content

Security Deep Dive

InditexTech/mcp-teams-server

Security posture and CVE patch evidence from tracked releases.

Back to Tool

No CVEs tracked against v1.0.9.

✗ Signed ✗ SLSA — SBOM ✓ Security policy Monthly cadence · 35d 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: 21d ago
Release cadence: monthly Present
35d 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
7.9/10 Security Score
8.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

1.00 / 1.0

1d stale

scorecard

3.44 / 4.0

Score 8.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

8.6

40%

scorecard score: 8.6 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.

Scorecard

Scorecard 8.6/10

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

Check Score Reason
Security-Policy 10 security policy file detected
Code-Review 7 Found 5/7 approved changesets -- score normalized to 7
Maintained 10 20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Dependency-Update-Tool 10 update tool detected
Binary-Artifacts 10 no binaries found in the repo
Token-Permissions 8 detected GitHub workflow tokens with excessive permissions
Dangerous-Workflow 10 no dangerous workflow patterns detected
Vulnerabilities 10 0 existing vulnerabilities detected
CII-Best-Practices 2 badge detected: InProgress
SAST 10 SAST tool is run on all commits
Signed-Releases -1 no releases found
License 10 license file detected
Fuzzing 0 project is not fuzzed
Branch-Protection 8 branch protection is not maximal on development and all release branches
Packaging 10 packaging workflow detected
Contributors 10 project has 4 contributing companies or organizations
CI-Tests 10 7 out of 7 merged PRs checked by a CI test -- score normalized to 10
Pinned-Dependencies 8 dependency not pinned by hash detected -- score normalized to 8

Beta — feedback welcome: [email protected]