Security Deep Dive
Nebula
Security posture and CVE patch evidence from tracked releases.
No known vulnerabilities in v1.10.3.
2 CVEs patched in tracked history. Median patch time: 0 days.
Versions by Severity
CVEs are attributed to tracked releases published before the patch release.
| Version | Published | C | H | M | L | KEV | Notes |
|---|---|---|---|---|---|---|---|
| v1.10.3 | 2026-02-06 | — | — | — | — | — | |
| v1.10.2 | 2026-01-21 | — | 1 | — | — | — |
—
|
| v1.10.1 | 2026-01-16 | — | 1 | — | — | — |
—
|
Trust Signals — 4 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
7d stale
scorecard
2.44 / 4.0
Score 6.1/10
cve health
2.50 / 2.5
No open CVEs
patch speed
0.50 / 0.5
0d avg
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
6.1
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 0.0/100Scorecard
Scorecard 6.1/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Maintained | 10 | 30 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10 |
| Security-Policy | 10 | security policy file detected |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| Code-Review | 10 | all changesets reviewed |
| Binary-Artifacts | 6 | binaries present in source code |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 10 | project is fuzzed |
| License | 10 | license file detected |
| Packaging | 10 | packaging workflow 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 |
| Pinned-Dependencies | 0 | dependency not pinned by hash detected -- score normalized to 0 |
| Signed-Releases | 0 | Project has not signed or included provenance with any releases. |
| SAST | 0 | SAST tool is not run on all commits -- score normalized to 0 |
OpenSSF Badge
Badge indicates adherence to open-source best practices.
CVE Patch History
Median patch time: 0 daysTracks CVEs that were addressed in tagged releases. Shorter gap between disclosure and patch = faster response. EPSS = predicted probability of exploitation in next 30 days (FIRST.org); colored at ≥90%ile and ≥50%ile.
CVEs Patched by Year
| CVE | Severity | EPSS | Disclosed | Fixed in | Days to fix | vs Ecosystem Median | KEV |
|---|---|---|---|---|---|---|---|
| GHSA-69x3-g4r3-p962 | High | — | — | v1.10.3 | — | — | — |
| GO-2026-4458 | unknown | — | — | v1.10.3 | — | — | — |
KEV = CISA Known Exploited Vulnerabilities catalog — actively exploited in the wild.
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
0
No dependency CVEs are currently attached to the latest SBOM scan. Re-run release ingestion if the latest release does not have SBOM coverage yet.