svyatov/sec_id holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (86/100) and lowest on Community & Adoption (53/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.
86
overall / 100
Excellent
Software health index
Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.
86
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
Score profile
Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.
The weighted overall 72 is calibrated to 86 on the published index scale (record calibration 2026-08-02).
Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25
Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40
No advisories left outstanding — no advisory carries a publication date
Inputs used
source
osv
advisories
0
affected_packages
0
assessed_packages
77
unassessed_packages
0
affected_by_severity
none
direct_affected_packages
0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 77 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.
How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.
API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20
MCP server — not applicable to this kind of software
40/40
Runnable examples — examples
Inputs used
example_dirs
examples
has_mcp_signal
no
api_schema_files
—
interfaces_expected_of
—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.
Key facts
8GitHub stars
2contributors
115commits, last 12 months
4days since last push
18releases
1bus factor
0open issues
RubyGemspackage ecosystems
Data collection warnings
Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
Star history carried forward from 2026-07-03: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 8 stars today.
More detail
Star and fork history 8 ★ / 1 ⇿
8Stars
1Forks
13Releases
When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.
Star history is shown as collected on 2026-07-03. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.
Major 5Minor 7Patch 1
Each point covers 7 days.
OpenSSF Scorecard 7.7 / 10
7.7aggregate
Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-12 13:14 UTC
Full resolved dependency set from the GitHub dependency graph: 13 direct and 64 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
Registry
Package
Version
Relation
RubyGems
activemodel
8.1.3.1
direct
RubyGems
benchmark-ips
2.15.1
direct
RubyGems
railties
8.1.3.1
direct
RubyGems
rake
13.4.2
direct
RubyGems
rbs
4.2.0
direct
RubyGems
rspec
3.13.2
direct
RubyGems
rspec_junit_formatter
0.6.0
direct
RubyGems
rubocop
1.90.0
direct
RubyGems
rubocop-rspec
3.10.2
direct
RubyGems
simplecov
1.1.1
direct
RubyGems
simplecov-cobertura
4.0.0
direct
RubyGems
steep
2.1.0
direct
RubyGems
yard
0.9.45
direct
RubyGems
actionpack
8.1.3.1
indirect
RubyGems
actionview
8.1.3.1
indirect
RubyGems
activesupport
8.1.3.1
indirect
RubyGems
ast
2.4.3
indirect
RubyGems
base64
0.3.0
indirect
RubyGems
bigdecimal
4.1.2
indirect
RubyGems
builder
3.3.0
indirect
RubyGems
concurrent-ruby
1.3.8
indirect
RubyGems
connection_pool
3.0.2
indirect
RubyGems
crass
1.0.7
indirect
RubyGems
csv
3.3.6
indirect
RubyGems
diff-lcs
1.6.2
indirect
RubyGems
drb
2.2.3
indirect
RubyGems
erb
6.0.7
indirect
RubyGems
erubi
1.13.1
indirect
RubyGems
ffi
1.17.4
indirect
RubyGems
fileutils
1.8.0
indirect
RubyGems
i18n
1.15.2
indirect
RubyGems
io-console
0.9.2
indirect
RubyGems
irb
1.18.0
indirect
RubyGems
json
2.21.2
indirect
RubyGems
language_server-protocol
3.17.0.6
indirect
RubyGems
lint_roller
1.1.0
indirect
RubyGems
listen
3.10.0
indirect
RubyGems
logger
1.7.0
indirect
RubyGems
loofah
2.25.2
indirect
RubyGems
minitest
6.0.6
indirect
RubyGems
nokogiri
1.19.4
indirect
RubyGems
parallel
2.1.0
indirect
RubyGems
parser
3.3.12.0
indirect
RubyGems
pp
0.6.4
indirect
RubyGems
prettyprint
0.2.0
indirect
RubyGems
prism
1.9.0
indirect
RubyGems
racc
1.8.1
indirect
RubyGems
rack
3.2.7
indirect
RubyGems
rack-session
2.1.2
indirect
RubyGems
rack-test
2.2.0
indirect
RubyGems
rackup
2.3.1
indirect
RubyGems
rails-dom-testing
2.3.0
indirect
RubyGems
rails-html-sanitizer
1.7.1
indirect
RubyGems
rainbow
3.1.1
indirect
RubyGems
rb-fsevent
0.11.2
indirect
RubyGems
rb-inotify
0.11.1
indirect
RubyGems
rdoc
8.0.0
indirect
RubyGems
regexp_parser
2.12.0
indirect
RubyGems
reline
0.7.0
indirect
RubyGems
rexml
3.4.4
indirect
RubyGems
rspec-core
3.13.6
indirect
RubyGems
rspec-expectations
3.13.5
indirect
RubyGems
rspec-mocks
3.13.8
indirect
RubyGems
rspec-support
3.13.7
indirect
RubyGems
rubocop-ast
1.50.0
indirect
RubyGems
ruby-progressbar
1.13.0
indirect
RubyGems
securerandom
0.4.1
indirect
RubyGems
strscan
3.1.8
indirect
RubyGems
terminal-table
4.0.0
indirect
RubyGems
thor
1.5.0
indirect
RubyGems
tsort
0.2.0
indirect
RubyGems
tzinfo
2.0.6
indirect
RubyGems
unicode-display_width
3.2.0
indirect
RubyGems
unicode-emoji
4.2.0
indirect
RubyGems
uri
1.1.1
indirect
RubyGems
useragent
0.16.11
indirect
RubyGems
zeitwerk
2.8.3
indirect
Dependency advisories 0
This repository publishes no package the index resolves, so its own dependency graph was assessed — 77 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct.
No known advisories affect the assessed dependencies.
An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.
Raw JSON report machine-readable
Feedback
Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.
Related records
Inspected repositories sharing catalogue tags or ecosystems with svyatov/sec_id. Read them side by side →
Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.
Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.