Skip to content
Tools / neovim / Security

Security Deep Dive

neovim

Security posture and CVE patch evidence from tracked releases.

Back to Tool

Open CVEs reported against v0.12.2.

See the CVE patch history below for context.

— Signed — SLSA — SBOM ✗ Security policy Weekly cadence · 7d 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: 22d ago
Release cadence: weekly Present
7d median over recent releases Release history
Latest release: 1mo ago
Maintainer active Present
Recent commit activity Repository
Last commit: 6d 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
5.0/10 Security Score
4.5/10 Scorecard
Pending CVE Patch Speed
Open CVEs Open CVEs detected for latest version.

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

6d stale

scorecard

1.80 / 4.0

Score 4.5/10

cve health

0.00 / 2.5

Open CVEs detected

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

0.0

25%

direct cves: open cve scan: available

Release responsiveness

release responsiveness

10.0

5%

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.5

40%

scorecard score: 4.5 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 6d

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.5/10

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

Check Score Reason
Dangerous-Workflow -1 no workflows found
Token-Permissions -1 No tokens found
Code-Review 2 Found 4/20 approved changesets -- score normalized to 2
Packaging -1 packaging workflow not detected
Maintained 10 30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices 0 no effort to earn an OpenSSF best practices badge detected
Security-Policy 0 security policy file not detected
Binary-Artifacts 10 no binaries found in the repo
License 9 license file detected
Pinned-Dependencies -1 no dependencies found
Fuzzing 0 project is not fuzzed
Branch-Protection 3 branch protection is not maximal on development and all release branches
Signed-Releases 0 Project has not signed or included provenance with any releases.
SAST 10 SAST tool is run on all commits

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Beta — feedback welcome: [email protected]