Tools / Plaso / Security

Security Deep Dive

Plaso

Security posture and CVE patch evidence from tracked releases.

Back to Tool

5 critical dependency CVEs affects 20260512.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA — SBOM ✗ Security policy Unknown cadence Active maintainer

Trust Signals — 1 of 9 Present

Evidence already collected from releases and repository metadata.

1/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: 20d ago

Release cadence Unknown

12-release median Release history

Latest release: 22d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 7d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 22d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 22d ago

Signing assets Not active yet

.sig, .crt, cosign.pub, or similar Release asset

Latest release: 22d ago

4.0/10 Security Score

5.6/10 Scorecard

Dependency Exposure 21 transitive dependency CVEs found in the latest SBOM. 5 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

7d stale

scorecard

2.24 / 4.0

Score 5.6/10

cve health

0.00 / 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

-1.50 / 10.0

Risk 30.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

7.0

10%

supply chain risk: 30.0 transitive cves: 5c/5h

Provenance trust

provenance trust

5.6

40%

scorecard score: 5.6 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 7d

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 30.0/100

5 Transitive critical CVEs

0 KEV-transitive CVEs

100% Dependency freshness

Scorecard

Scorecard 5.6/10

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

Check	Score	Reason
Code-Review	2	Found 7/30 approved changesets -- score normalized to 2
Dangerous-Workflow	10	no dangerous workflow patterns detected
Maintained	10	30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
Packaging	-1	packaging workflow not detected
Token-Permissions	10	GitHub workflow tokens follow principle of least privilege
CII-Best-Practices	0	no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts	7	binaries present in source code
Security-Policy	0	security policy file not detected
License	10	license file detected
Fuzzing	0	project is not fuzzed
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
Signed-Releases	8	5 out of the last 5 releases have a total of 5 signed artifacts.
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

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

129 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 (0) All (21)

Critical 5 High 5 Medium 10 Low 1

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2009-5042	critical	—	docutils	—	20260512
CVE-2017-18342	critical	—	pyyaml	—	20260512
CVE-2019-20477	critical	—	pyyaml	—	20260512
CVE-2020-14343	critical	—	pyyaml	—	20260512
CVE-2020-1747	critical	—	pyyaml	—	20260512
CVE-2018-18074	high	—	requests	—	20260512
CVE-2019-18874	high	—	psutil	—	20260512
CVE-2022-4899	high	—	zstd	—	20260512
CVE-2023-28859	high	—	redis	—	20260512
CVE-2023-37920	high	—	certifi	—	20260512
CVE-2014-1829	medium	—	requests	—	20260512
CVE-2014-1830	medium	—	requests	—	20260512
CVE-2015-2296	medium	—	requests	—	20260512
CVE-2022-23491	medium	—	certifi	—	20260512
CVE-2023-28858	medium	—	redis	—	20260512
CVE-2023-32681	medium	—	requests	—	20260512
CVE-2024-35195	medium	—	requests	—	20260512
CVE-2024-47081	medium	—	requests	—	20260512
CVE-2025-69534	medium	—	markdown	—	20260512
CVE-2026-25645	medium	—	requests	—	20260512
CVE-2024-39689	low	—	certifi	—	20260512

Showing 21 of 21