Tools / Squidex / Security

Security Deep Dive

Squidex

Security posture and CVE patch evidence from tracked releases.

Back to Tool

No CVEs tracked against 7.23.0.

— Signed — SLSA — SBOM ✗ Security policy Dormant cadence · 132d median Active 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 Absent

GitHub repository metadata Repository policy

Checked: 21d ago

Release cadence: dormant Present

132d median over recent releases Release history

Latest release: 1mo ago

Maintainer active Present

Recent commit activity Repository

Last commit: 7d 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

6.3/10 Security Score

4.4/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

7d stale

scorecard

1.76 / 4.0

Score 4.4/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

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

4.4

40%

scorecard score: 4.4 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 7d

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 4.4/10

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

Check	Score	Reason
Maintained	10	19 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Code-Review	2	Found 6/28 approved changesets -- score normalized to 2
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
License	10	license file detected
Binary-Artifacts	10	no binaries found in the repo
Signed-Releases	0	Project has not signed or included provenance with any releases.
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
Fuzzing	0	project is not fuzzed
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.