BlackHartBlackHart
Scores/Lido/Provenance/Operational Security
D11

Operational Security

Incident response speed, deployment hygiene, key management, monitoring infrastructure, and emergency history.

Weight 10%60% confidence
66
Moderate
info

How This Score Is Built

Incident response speed, deployment hygiene, key management, monitoring infrastructure, and emergency history.

+23Strong positive
+12Positive
+5Slight positive
−15Strong negative
−8Negative
−3Slight negative

Scoring Tree

BRI Formula
300 + 700 × ∏(Dᵢ/100)^wᵢ
847
Current BRI
D11Operational Security
Weight 10%
66
(66/100)^0.1 = 0.9593
Sub-Scores
Development Practices
44
Incident Response
65
Deployment Hygiene
73
Key Management
70
Monitoring
85
Emergency History
75
Contributing Factors
+16Commit signing: 100% verified
+16SECURITY.md present (detailed)
+16Moderate development (17 commits/month)
+16Multiple monitoring repos found: terra-monitors, depositor-bot, web3-flashbots
-17No branch protection detected
-17CI/CD present but unstable (40% success)
0Incident response time not available (using commit frequency proxy)
0Key management score defaulted (no on-chain data available)
Evidence Sources
githubMay 17sha256:f857eaddc3b4....View
githubMay 20sha256:913ad46e0cba....View
github_apiMay 20sha256:913ad46e0cba4...View

Sub-Score Breakdown

Development Practices
44
Incident Response
65
Deployment Hygiene
73
Key Management
70
Monitoring
85
Emergency History
75

Score Composition

-17

No branch protection detected

Negativeopen_in_newrepos/lidofinance/lido-dao/*May 20, 2026
-17

CI/CD present but unstable (40% success)

Negativeopen_in_newrepos/lidofinance/lido-dao/*May 20, 2026
0

Incident response time not available (using commit frequency proxy)

Neutralopen_in_newrepos/lidofinance/lido-dao/*May 20, 2026
0

Key management score defaulted (no on-chain data available)

Neutralopen_in_newrepos/lidofinance/lido-dao/*May 20, 2026
+16

Commit signing: 100% verified

Positiveopen_in_newrepos/lidofinance/lido-dao/*May 20, 2026
+16

SECURITY.md present (detailed)

Positiveopen_in_newrepos/lidofinance/lido-dao/*May 20, 2026
+16

Moderate development (17 commits/month)

Positiveopen_in_newrepos/lidofinance/lido-dao/*May 20, 2026
+16

Multiple monitoring repos found: terra-monitors, depositor-bot, web3-flashbots

Positiveopen_in_newrepos/lidofinance/lido-dao/*May 20, 2026

Evidence Chain (3 files)

GitHub APIMay 20, 2026, 04:49 AM
open_in_newExternal: repos/lidofinance/lido-dao/*
sha256:913ad46e0cba4bb60641f9d...
GitHub APIMay 20, 2026, 04:49 AM
open_in_newGitHub (lidofinance/lido-dao)
branch protection: No
required reviews: 0
ci success rate: 40%
has ci: Yes
signing ratio: 1
commits 90d: 50
pr review ratio: 43%
dependabot: No
security policy: Yes
sha256:913ad46e0cba...
BlackHart AnalysisMay 17, 2026, 01:20 AM
open_in_newOperational Security — GitHub Repository
branch protection: No
required reviews: 0
ci success rate: 40%
has ci: Yes
signing ratio: 1
commits 90d: 50
pr review ratio: 47%
dependabot: No
security policy: Yes
sha256:f857eaddc3b4...

Score History

66(+66)
No branch protection detected
68(+68)
No branch protection detected
Methodology: 2.1Formula: 1.1Weights: 1.1
How is Operational Security scored?← Back to Provenance Ledger