Skip to content
Tools / rspamd / Security

Security Deep Dive

rspamd

Security posture and CVE patch evidence from tracked releases.

Back to Tool

5 high-severity dependency CVEs affects 4.0.1.

Review the dependency vulnerabilities below.

✗ Signed ✗ SLSA ✓ SBOM ✗ Security policy Unknown cadence Active maintainer

Trust Signals — 2 of 9 Present

Evidence already collected from releases and repository metadata.

2/9 Present
Signed releases Absent
Latest release artifact signature None
Last verified: 18d ago
SLSA provenance Absent
Attestation predicate level Latest release
Last verified: 18d ago
SBOM published Present
GitHub SBOM API Latest release
Last verified: 28d ago
SECURITY.md Absent
GitHub repository metadata Repository policy
Checked: 22d ago
Release cadence Unknown
12-release median Release history
Latest release: 1mo ago
Maintainer active Present
Recent commit activity Repository
Last commit: 2d 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
5.3/10 Security Score
4.7/10 Scorecard
Dependency Exposure 9 transitive dependency CVEs found in the latest SBOM.

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

2d stale

scorecard

1.88 / 4.0

Score 4.7/10

cve health

1.50 / 2.5

No open 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.29 / 10.0

Risk 12.9/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

6.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

8.7

10%

supply chain risk: 12.95 transitive cves: 0c/6h

Provenance trust

provenance trust

4.7

40%

scorecard score: 4.7 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 2d

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 12.9/100
0 Transitive critical CVEs
0 KEV-transitive CVEs
52% Dependency freshness

Scorecard

Scorecard 4.7/10

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

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

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

221 dependencies scanned View full dependency list →

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

Critical

0

High

5

Medium

4

Low

0

Unknown

0

High 5 Medium 4
CVE Severity KEV Dependency Affected version Cleared in release
CVE-2026-32141 high flatted 3.3.3
CVE-2026-33228 high flatted 3.3.3
CVE-2026-33671 high picomatch 4.0.3
CVE-2026-6321 high fast-uri 3.0.6
CVE-2026-6322 high fast-uri 3.0.6
CVE-2026-1839 medium transformers 4.53.0
CVE-2026-33672 medium picomatch 4.0.3
CVE-2026-33750 medium brace-expansion 5.0.4
CVE-2026-41305 medium postcss 8.5.6

Showing 9 of 11

Beta — feedback welcome: [email protected]