Skip to content
Tools / iotdb / Security

Security Deep Dive

iotdb

Security posture and CVE patch evidence from tracked releases.

Back to Tool

Open CVEs reported against v2.0.8.

See the CVE patch history below for context.

✗ Signed ✗ SLSA — SBOM ✗ Security policy Monthly cadence · 39d median Active maintainer

Trust Signals — 2 of 9 Present

Evidence already collected from releases and repository metadata.

2/9 Present
Signed releases Absent
Latest release artifact signature None
Last verified: 8d ago
SLSA provenance Absent
Attestation predicate level Latest release
Last verified: 8d ago
SBOM published Unknown
GitHub SBOM API Latest release
SECURITY.md Absent
GitHub repository metadata Repository policy
Checked: 17d ago
Release cadence: monthly Present
39d 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
5.3/10 Security Score
5.2/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

3d stale

scorecard

2.08 / 4.0

Score 5.2/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

5.2

40%

scorecard score: 5.2 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.

Scorecard

Scorecard 5.2/10

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

Check Score Reason
Code-Review 6 Found 19/30 approved changesets -- score normalized to 6
Maintained 10 30 commit(s) and 5 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
Packaging -1 packaging workflow not detected
Dangerous-Workflow 10 no dangerous workflow patterns detected
Token-Permissions 0 detected GitHub workflow tokens with excessive permissions
License 10 license file detected
Security-Policy 10 security policy file detected
Signed-Releases 0 Project has not signed or included provenance with any releases.
Binary-Artifacts 10 no binaries found in the repo
Fuzzing 0 project is not fuzzed
Branch-Protection 0 branch protection not enabled on development/release branches
Pinned-Dependencies 0 dependency not pinned by hash detected -- score normalized to 0
SAST 10 SAST tool detected

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Beta — feedback welcome: [email protected]