Skip to content
Tools / OpenFaaS / Security

Security Deep Dive

OpenFaaS

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 critical dependency CVE affects 0.27.13.

Audit transitive dependencies; consider upgrading or pinning replacements.

— 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 Present
GitHub SBOM API Latest release
Last verified: 28d ago
SECURITY.md Absent
GitHub repository metadata Repository policy
Checked: 17d ago
Release cadence Unknown
12-release median Release history
Latest release: 9mo ago
Maintainer sporadic Present
Recent commit activity Repository
Last commit: 2mo ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 9mo ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 9mo ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 9mo ago
4.3/10 Security Score
3.8/10 Scorecard
Dependency Exposure 12 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

0.90 / 1.0

62d stale

scorecard

1.52 / 4.0

Score 3.8/10

cve health

1.00 / 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.40 / 10.0

Risk 14.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

4.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.6

10%

supply chain risk: 14.0 transitive cves: 1c/5h

Provenance trust

provenance trust

3.8

40%

scorecard score: 3.8 openssf badge: none

Maintainer health

maintainer health

9.0

10%

activity freshness: 62d

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

Scorecard

Scorecard 3.8/10

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

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

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

49 dependencies scanned View full dependency list →

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

Critical

1

High

5

Medium

3

Low

1

Unknown

2

Critical 1 High 5 Medium 3 Low 1 Unknown 2
CVE Severity KEV Dependency Affected version Cleared in release
CVE-2021-3127 critical github.com/nats-io/jwt 1.2.2
CVE-2022-21698 high github.com/prometheus/client_golang 1.9.0
CVE-2022-24450 high github.com/nats-io/nats-streaming-server 0.20.0
CVE-2022-26652 high github.com/nats-io/nats-streaming-server 0.20.0
CVE-2022-29946 high github.com/nats-io/nats-streaming-server 0.20.0
CVE-2023-2253 high github.com/docker/distribution 2.7.1+incompatible
CVE-2022-29526 medium golang.org/x/sys 0.0.0-20210119212857-b64e53b001e4
CVE-2025-47914 medium golang.org/x/crypto 0.41.0
CVE-2025-58181 medium golang.org/x/crypto 0.41.0
GHSA-qq97-vm5h-rrhg low github.com/docker/distribution 2.7.1+incompatible
CVE-2025-47913 unknown golang.org/x/crypto 0.41.0
GO-2022-0379 unknown github.com/docker/distribution 2.7.1+incompatible

Showing 12 of 12

Beta — feedback welcome: [email protected]