Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-13 02:34 UTC

omgovich / colord

👑 A tiny yet powerful tool for high-performance color manipulations and conversions

TypeScriptMIT★ 1,878 stars⑂ 63 forkssince Nov 2020View on GitHub ↗

omgovich/colord holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (72/100) and lowest on Vitality (40/100). It was last updated 82 days ago. A single contributor accounts for most of its recent work.

56
overall / 100
Moderate

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.

56
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)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

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 54 is calibrated to 56 on the published index scale (record calibration 2026-08-02).

Ownership

Vlad ShilovPersonal account
299 followers45 public repossince Feb 2010Variant.net

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmcolord2.9.376,337,573491463 days agocolorparserconverttinyhexrgbhslhsvhwblablchxyzcsscolor-namesa11ycmykmixminifyharmonies

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

40Weak · 21% of overall
How it's scored
18/36Push recencylast push 82 days ago
0.7/36Commit cadence1/52 weeks with commits
5.4/18Commit volume3 commits in the last year
3/10OpenSSF Scorecard: Maintained3 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year3
human_commit_share0.99
days_since_last_push82
active_weeks_last_year1
How it's scored
27/27Ships releases14 releases published
0/36Release recencylatest release 1,759 days ago
27/27Release cadencea release every ~19.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count14
latest_release_tagv2.9
releases_from_tagsno
days_since_latest_release1,759
mean_days_between_releases19.2
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

72Good · 17% of overall
How it's scored
53.1/60Stars1,878 stars
14.9/25Forks63 forks
5.3/15Watchers10 watchers
Inputs used
forks63
stars1,878
watchers10
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges25
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadgen.net, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads76,337,573 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagescolord
dependents
ecosystemsnpm
total_downloads
monthly_downloads76,337,573
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

57Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.8/22.5Commit distributiontop contributor authored 79% of commits
13.5/13.5Contributor breadth10 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled10
top_contributor_share0.787
How it's scored
24.9/42Issue resolution59% of issues closed
26.8/30PR acceptance58/65 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 4/13 approved changesets -- score normalized to 3
Inputs used
merged_prs58
open_issues26
closed_issues38
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.594
closed_unmerged_prs7
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
17.8/25Owner reach299 followers of omgovich
24.1/25Track record45 public repos, account ~16 yr old
Inputs used
followers299
owner_typeUser
is_verified
owner_loginomgovich
public_repos45
account_age_days6,018
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on npm
4/35Publish recencylatest publish 1,463 days ago
20/20Version history49 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagescolord
ecosystemsnpm
any_deprecatedno
min_days_since_publish1,463

Engineering Quality

Are baseline engineering and documentation practices in place?

57Moderate · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests2 out of 8 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://colord.omgovich.ru
10/10Repository description
10/10Topics17 topics
0/10Wiki
Inputs used
topicscolor, parser, converter, hex, rgb, hsl, hsv, tiny, color-names, a11y, css-color, zero-dependency, lch, lab, hwb, xyz, hacktoberfest
has_wikino
homepagehttps://colord.omgovich.ru
docs_sitehttps://colord.omgovich.ru
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

46Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0.5/2.5CI-Tests2 out of 8 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-ReviewFound 4/13 approved changesets -- score normalized to 3
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
2.2/7.5Maintained3 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 3
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities50 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.6
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

AI Readiness

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.

47Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
14/40Legible commit history26 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.263
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance1 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.01
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/46 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes20,324
source_files_sampled46
oversized_source_files0

Key facts

1,878GitHub stars
10contributors
3commits, last 12 months
82days since last push
14releases
1bus factor
26open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 63 ⇿
0Stars
63Forks
14Releases

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.

013253850636222021-042023-112026-07
Major 0Minor 0Patch 0

Each point covers 5 days.

OpenSSF Scorecard 4.6 / 10
4.6aggregate

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-08-13 02:33 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
2CI-Tests2 out of 8 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 4/13 approved changesets -- score normalized to 3
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
3Maintained3 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 3
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities50 existing vulnerabilities detected
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.

The message is kept through sign-in.

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.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.