Tools / Real Intelligence Threat Analysis (RITA) / Security

Security Deep Dive

Real Intelligence Threat Analysis (RITA)

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 critical dependency CVE affects v5.1.2.

Audit transitive dependencies; consider upgrading or pinning replacements.

— 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: 21d ago

Release cadence Unknown

12-release median Release history

Latest release: 28d ago

Maintainer active Present

Recent commit activity Repository

Last commit: today

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 28d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 28d ago

Signing assets Not active yet

.sig, .crt, cosign.pub, or similar Release asset

Latest release: 28d ago

3.5/10 Security Score

4.5/10 Scorecard

Dependency Exposure 24 transitive dependency CVEs found in the latest SBOM. 1 critical.

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

Up to date

scorecard

1.80 / 4.0

Score 4.5/10

cve health

0.00 / 2.5

⚠ No direct scan — 1c/10h transitive CVEs

patch speed

0.50 / 0.5

⚠ Estimated — no CVE patch history

kev exposure

1.50 / 1.5

No KEV exposure

supply chain risk

-1.50 / 10.0

Risk 24.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

7.6

10%

supply chain risk: 24.0 transitive cves: 1c/10h

Provenance trust

provenance trust

4.5

40%

scorecard score: 4.5 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 0d

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.

Supply Chain Risk

Risk 24.0/100

1 Transitive critical CVEs

0 KEV-transitive CVEs

100% Dependency freshness

Scorecard

Scorecard 4.5/10

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

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

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

256 dependencies scanned View full dependency list →

Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.

Critical

High

Medium

Low

Unknown

Still affecting latest (24) All (28)

Critical 1 High 8 Medium 10 Unknown 5

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2026-33186	critical	—	google.golang.org/grpc	v1.59.0	v5.1.2
CVE-2024-25621	high	—	github.com/containerd/containerd	v1.7.17	v5.1.2
CVE-2025-22868	high	—	golang.org/x/oauth2	v0.15.0	v5.1.2
CVE-2025-22869	high	—	golang.org/x/crypto	v0.33.0	v5.1.2
CVE-2026-24051	high	—	go.opentelemetry.io/otel/sdk	v1.24.0	v5.1.2
CVE-2026-33747	high	—	github.com/moby/buildkit	v0.13.2	v5.1.2
CVE-2026-33748	high	—	github.com/moby/buildkit	v0.13.2	v5.1.2
CVE-2026-35469	high	—	github.com/moby/spdystream	v0.2.0	v5.1.2
CVE-2026-39883	high	—	go.opentelemetry.io/otel/sdk	v1.24.0	v5.1.2
CVE-2024-10846	medium	—	github.com/compose-spec/compose-go/v2	v2.1.1	v5.1.2
CVE-2024-40635	medium	—	github.com/containerd/containerd	v1.7.17	v5.1.2
CVE-2025-0495	medium	—	github.com/docker/buildx	v0.14.1	v5.1.2
CVE-2025-22870	medium	—	golang.org/x/net	v0.35.0	v5.1.2
CVE-2025-22872	medium	—	golang.org/x/net	v0.35.0	v5.1.2
CVE-2025-47914	medium	—	golang.org/x/crypto	v0.33.0	v5.1.2
CVE-2025-58181	medium	—	golang.org/x/crypto	v0.33.0	v5.1.2
CVE-2025-64329	medium	—	github.com/containerd/containerd	v1.7.17	v5.1.2
CVE-2026-39882	medium	—	go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp	v0.42.0	v5.1.2
CVE-2026-39882	medium	—	go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp	v1.21.0	v5.1.2
CVE-2025-47911	unknown	—	golang.org/x/net	v0.35.0	v5.1.2
CVE-2025-47913	unknown	—	golang.org/x/crypto	v0.33.0	v5.1.2
CVE-2025-58190	unknown	—	golang.org/x/net	v0.35.0	v5.1.2
CVE-2025-62725	unknown	—	github.com/docker/compose/v2	v2.27.1	v5.1.2
CVE-2026-33814	unknown	—	golang.org/x/net	v0.35.0	v5.1.2

Showing 24 of 28