Security Deep Dive
kimai
Security posture and CVE patch evidence from tracked releases.
1 critical dependency CVE affects 2.58.0.
Audit transitive dependencies; consider upgrading or pinning replacements.
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
2d stale
scorecard
2.04 / 4.0
Score 5.1/10
cve health
0.00 / 2.5
⚠ No direct scan — 1c/21h 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.50 / 10.0
Risk 46.7/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
5.3
10%
Provenance trust
provenance trust
5.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 46.7/100Scorecard
Scorecard 5.1/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Packaging | -1 | packaging workflow not detected |
| Code-Review | 3 | Found 10/30 approved changesets -- score normalized to 3 |
| Maintained | 10 | 28 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10 |
| Token-Permissions | -1 | No tokens found |
| Security-Policy | 9 | security policy file detected |
| Dangerous-Workflow | -1 | no workflows found |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Binary-Artifacts | 10 | no binaries found in the repo |
| Fuzzing | 0 | project is not fuzzed |
| License | 10 | license file detected |
| Signed-Releases | -1 | no releases found |
| 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 |
| SAST | 0 | SAST tool is not run on all commits -- score normalized to 0 |
| Pinned-Dependencies | 0 | dependency not pinned by hash detected -- score normalized to 0 |
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
1
High
21
Medium
19
Low
5
Unknown
0
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2020-19825 | critical | — | kimai/kimai | 0 | 2.57.0 |
| CVE-2023-46245 | high | — | kimai/kimai | 0 | 2.57.0 |
| CVE-2023-53957 | high | — | kimai/kimai | 0 | 2.57.0 |
| CVE-2026-24842 | high | — | tar | 7.5.6 | 2.57.0 |
| CVE-2026-25547 | high | — | @isaacs/brace-expansion | 5.0.0 | 2.57.0 |
| CVE-2026-26960 | high | — | tar | 7.5.6 | 2.57.0 |
| CVE-2026-26996 | high | — | minimatch | 3.1.2 | 2.57.0 |
| CVE-2026-27903 | high | — | minimatch | 3.1.2 | 2.57.0 |
| CVE-2026-27904 | high | — | minimatch | 3.1.2 | 2.57.0 |
| CVE-2026-29063 | high | — | immutable | 5.1.4 | 2.57.0 |
| CVE-2026-29074 | high | — | svgo | 4.0.0 | 2.57.0 |
| CVE-2026-29786 | high | — | tar | 7.5.6 | 2.57.0 |
| CVE-2026-31802 | high | — | tar | 7.5.6 | 2.57.0 |
| CVE-2026-32141 | high | — | flatted | 3.3.3 | 2.57.0 |
| CVE-2026-33228 | high | — | flatted | 3.3.3 | 2.57.0 |
| CVE-2026-33671 | high | — | picomatch | 4.0.3 | 2.57.0 |
| CVE-2026-44728 | high | — | @babel/plugin-transform-modules-systemjs | 7.28.5 | 2.57.0 |
| CVE-2026-4800 | high | — | lodash | 4.17.23 | 2.57.0 |
| CVE-2026-6321 | high | — | fast-uri | 3.1.0 | 2.57.0 |
| CVE-2026-6322 | high | — | fast-uri | 3.1.0 | 2.57.0 |
| GHSA-534c-hcr7-67jg | high | — | kimai/kimai | 0 | 2.57.0 |
| GHSA-5c6j-r48x-rmvq | high | — | serialize-javascript | 6.0.2 | 2.57.0 |
| CVE-2019-25317 | medium | — | kimai/kimai | 0 | 2.57.0 |
| CVE-2024-29200 | medium | — | kimai/kimai | 0 | 2.57.0 |
| CVE-2025-69873 | medium | — | ajv | 8.17.1 | 2.57.0 |
| CVE-2026-23626 | medium | — | kimai/kimai | 0 | 2.57.0 |
| CVE-2026-28685 | medium | — | kimai/kimai | 0 | 2.57.0 |
| CVE-2026-2950 | medium | — | lodash | 4.17.23 | 2.57.0 |
| CVE-2026-33672 | medium | — | picomatch | 4.0.3 | 2.57.0 |
| CVE-2026-33750 | medium | — | brace-expansion | 1.1.12 | 2.57.0 |
| CVE-2026-34043 | medium | — | serialize-javascript | 6.0.2 | 2.57.0 |
| CVE-2026-40479 | medium | — | kimai/kimai | 0 | 2.57.0 |
| CVE-2026-40486 | medium | — | kimai/kimai | 0 | 2.57.0 |
| CVE-2026-41238 | medium | — | dompurify | 3.3.3 | 2.57.0 |
| CVE-2026-41239 | medium | — | dompurify | 3.3.3 | 2.57.0 |
| CVE-2026-41240 | medium | — | dompurify | 3.3.3 | 2.57.0 |
| CVE-2026-41305 | medium | — | postcss | 8.5.6 | 2.57.0 |
| CVE-2026-42338 | medium | — | ip-address | 10.1.0 | 2.57.0 |
| GHSA-39q2-94rc-95cp | medium | — | dompurify | 3.3.3 | 2.57.0 |
| GHSA-9g2q-w3w2-vf7q | medium | — | kimai/kimai | 0 | 2.57.0 |
| GHSA-vrqv-52x7-rm4v | medium | — | kimai/kimai | 0 | 2.57.0 |
| CVE-2024-4596 | low | — | kimai/kimai | 0 | 2.57.0 |
| CVE-2026-41498 | low | — | kimai/kimai | 0 | 2.57.0 |
| GHSA-3jp4-mhh4-gcgr | low | — | kimai/kimai | 0 | 2.57.0 |
| GHSA-jrc6-fmhw-fpq2 | low | — | kimai/kimai | 0 | 2.57.0 |
| GHSA-rh42-6rj2-xwmc | low | — | kimai/kimai | 0 | 2.57.0 |
Showing 46 of 46