Security Deep Dive
SolidInvoice
Security posture and CVE patch evidence from tracked releases.
No CVEs tracked against 2.3.17.
Trust Signals — 3 of 9 Present
Evidence already collected from releases and repository metadata.
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.92 / 4.0
Score 4.8/10
cve health
1.00 / 2.5
⚠ No direct scan — 0c/1h 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
-0.20 / 10.0
Risk 2.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
4.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
9.8
10%
Provenance trust
provenance trust
4.8
40%
Maintainer health
maintainer health
10.0
10%
Operational risk
operational risk
8.5
10%
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 2.0/100Scorecard
Scorecard 4.8/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Maintained | 10 | 30 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 10 |
| Packaging | -1 | internal error: internal error: invalid GitHub workflow: :89:0: could not parse as YAML: yaml: line 89: could not find expected ':' [syntax-check] |
| Code-Review | 0 | Found 0/13 approved changesets -- score normalized to 0 |
| Pinned-Dependencies | -1 | internal error: internal error: invalid GitHub workflow: :89:0: could not parse as YAML: yaml: line 89: could not find expected ':' [syntax-check] |
| Token-Permissions | -1 | internal error: internal error: invalid GitHub workflow: :89:0: could not parse as YAML: yaml: line 89: could not find expected ':' [syntax-check] |
| Dependency-Update-Tool | 10 | update tool detected |
| Security-Policy | 10 | security policy file detected |
| Dangerous-Workflow | -1 | internal error: internal error: invalid GitHub workflow: :89:0: could not parse as YAML: yaml: line 89: could not find expected ':' [syntax-check] |
| Binary-Artifacts | 10 | no binaries found in the repo |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Signed-Releases | 0 | Project has not signed or included provenance with any releases. |
| Fuzzing | 0 | project is not fuzzed |
| License | 10 | license file detected |
| Vulnerabilities | 0 | 28 existing vulnerabilities detected |
| SAST | -1 | internal error: internal error: invalid GitHub workflow: :89:0: could not parse as YAML: yaml: line 89: could not find expected ':' [syntax-check] |
| Branch-Protection | 0 | branch protection not enabled on development/release branches |
| CI-Tests | 10 | 9 out of 9 merged PRs checked by a CI test -- score normalized to 10 |
| Contributors | 10 | project has 11 contributing companies or organizations |
OpenSSF Badge
Badge indicates adherence to open-source best practices.
Dependency Vulnerabilities
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
0
High
0
Medium
0
Low
0
Unknown
2
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2026-33814 | unknown | — | golang.org/x/net | v0.52.0 | 2.3.17 |
| GO-2026-4442 | unknown | — | github.com/dunglas/frankenphp | v1.12.2 | 2.3.17 |
Showing 2 of 8