Security Deep Dive
ajitpratap0/GoSQLX
Security posture and CVE patch evidence from tracked releases.
No CVEs tracked against v1.14.0.
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
0.93 / 1.0
54d stale
scorecard
1.68 / 4.0
Score 4.2/10
cve health
2.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
0.00 / 10.0
Risk 0.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
10.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
10.0
10%
Provenance trust
provenance trust
4.2
40%
Maintainer health
maintainer health
9.3
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.
Scorecard
Scorecard 4.2/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Binary-Artifacts | 7 | binaries present in source code |
| Branch-Protection | 3 | branch protection is not maximal on development and all release branches |
| CI-Tests | 10 | 30 out of 30 merged PRs checked by a CI test -- score normalized to 10 |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Code-Review | 0 | Found 0/30 approved changesets -- score normalized to 0 |
| Contributors | 0 | project has 0 contributing companies or organizations -- score normalized to 0 |
| Dangerous-Workflow | -1 | internal error: internal error: invalid GitHub workflow: :85:0: could not parse as YAML: yaml: line 85: could not find expected ':' [syntax-check] |
| Dependency-Update-Tool | 10 | update tool detected |
| Fuzzing | 10 | project is fuzzed |
| License | 10 | license file detected |
| Maintained | 1 | 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1 |
| Packaging | -1 | internal error: internal error: invalid GitHub workflow: :85:0: could not parse as YAML: yaml: line 85: could not find expected ':' [syntax-check] |
| Pinned-Dependencies | -1 | internal error: internal error: invalid GitHub workflow: :85:0: could not parse as YAML: yaml: line 85: could not find expected ':' [syntax-check] |
| SAST | -1 | internal error: internal error: invalid GitHub workflow: :85:0: could not parse as YAML: yaml: line 85: could not find expected ':' [syntax-check] |
| Security-Policy | 10 | security policy file detected |
| Signed-Releases | 0 | Project has not signed or included provenance with any releases. |
| Token-Permissions | -1 | internal error: internal error: invalid GitHub workflow: :85:0: could not parse as YAML: yaml: line 85: could not find expected ':' [syntax-check] |
| Vulnerabilities | 0 | 74 existing vulnerabilities detected |
OpenSSF Badge
Badge indicates adherence to open-source best practices.