Tools / donetick / Security

Security Deep Dive

donetick

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 critical dependency CVE affects v0.1.75.

Audit transitive dependencies; consider upgrading or pinning replacements.

✗ Signed ✗ SLSA ✓ SBOM ✗ Security policy Weekly cadence · 1d median Active maintainer

Trust Signals — 3 of 9 Present

Evidence already collected from releases and repository metadata.

3/9 Present

Signed releases Absent

Latest release artifact signature None

Last verified: 7d ago

SLSA provenance Absent

Attestation predicate level Latest release

Last verified: 7d ago

SBOM published Present

GitHub SBOM API Latest release

Last verified: 28d ago

SECURITY.md Absent

GitHub repository metadata Repository policy

Checked: 21d ago

Release cadence: weekly Present

1d median over recent releases Release history

Latest release: 1mo ago

Maintainer active Present

Recent commit activity Repository

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

4.2/10 Security Score

Dependency Exposure 9 transitive dependency CVEs found in the latest SBOM. 1 critical.

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

3d stale

scorecard

2.00 / 4.0

⚠ Estimated — not yet collected

cve health

0.00 / 2.5

⚠ No direct scan — 1c/3h 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

-1.00 / 10.0

Risk 10.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

9.0

10%

supply chain risk: 10.0 transitive cves: 1c/3h

Provenance trust

provenance trust

5.0

40%

scorecard score: estimated openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 3d

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.

Supply Chain Risk

Risk 10.0/100

1 Transitive critical CVEs

0 KEV-transitive CVEs

100% Dependency freshness

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

176 dependencies scanned View full dependency list →

Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.

Critical

High

Medium

Low

Unknown

Still affecting latest (9) All (9)

Critical 1 High 3 Low 1 Unknown 4

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2026-33816	critical	—	github.com/jackc/pgx/v5	v5.5.5	—
CVE-2026-24051	high	—	go.opentelemetry.io/otel/sdk	v1.39.0	—
CVE-2026-29181	high	—	go.opentelemetry.io/otel	v1.39.0	—
CVE-2026-39883	high	—	go.opentelemetry.io/otel/sdk	v1.39.0	—
CVE-2026-41889	low	—	github.com/jackc/pgx/v5	v5.5.5	—
CVE-2020-8911	unknown	—	github.com/aws/aws-sdk-go	v1.55.7	—
CVE-2020-8912	unknown	—	github.com/aws/aws-sdk-go	v1.55.7	—
CVE-2026-33814	unknown	—	golang.org/x/net	v0.49.0	—
CVE-2026-33815	unknown	—	github.com/jackc/pgx/v5	v5.5.5	—

Showing 9 of 9