Skip to content
Tools / Sysmon for Linux / Security

Security Deep Dive

Sysmon for Linux

Security posture and CVE patch evidence from tracked releases.

Back to Tool

No CVEs tracked against 1.5.2.

— Signed — SLSA — SBOM ✗ Security policy Quarterly cadence · 45d 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: 21d ago
Release cadence: quarterly Present
45d median over recent releases Release history
Latest release: 27d ago
Maintainer active Present
Recent commit activity Repository
Last commit: 27d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 27d ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 27d ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 27d ago
8.3/10 Security Score
6.4/10 Scorecard

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

26d stale

scorecard

2.56 / 4.0

Score 6.4/10

cve health

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

0.00 / 10.0

Risk 0.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

10.0

25%

direct cves: clear 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

6.4

40%

scorecard score: 6.4 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 26d

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 6.4/10

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

Check Score Reason
Binary-Artifacts 10 no binaries found in the repo
Branch-Protection -1 internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration
CI-Tests 5 16 out of 30 merged PRs checked by a CI test -- score normalized to 5
CII-Best-Practices 0 no effort to earn an OpenSSF best practices badge detected
Code-Review 10 all changesets reviewed
Contributors 10 3 different organizations found -- score normalized to 10
Dangerous-Workflow 10 no dangerous workflow patterns detected
Dependency-Update-Tool 0 no update tool detected
Fuzzing 0 project is not fuzzed
License 10 license file detected
Maintained 9 7 commit(s) out of 30 and 4 issue activity out of 30 found in the last 90 days -- score normalized to 9
Packaging -1 no published package detected
Pinned-Dependencies 3 dependency not pinned by hash detected -- score normalized to 3
SAST 0 SAST tool is not run on all commits -- score normalized to 0
Security-Policy 10 security policy file detected
Signed-Releases 0 0 out of 5 artifacts are signed or have provenance
Token-Permissions 10 GitHub workflow tokens follow principle of least privilege
Vulnerabilities 10 no vulnerabilities detected

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Beta — feedback welcome: [email protected]