Public record
Software health reportschema 0.15.0 · metrics 2.10.0 · 2026-07-19 15:49 UTC

microlinkhq / unavatar

Get unified user avatar from social networks, including Instagram, SoundCloud, Telegram, Twitter, YouTube & more.

HTMLMIT★ 1,448 stars⑂ 86 forkssince Apr 2018View on GitHub ↗

microlinkhq/unavatar holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (93/100) and lowest on AI Readiness (24/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

80
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.

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

Ownership

microlink.ioOrganization
364 followers62 public repossince Jun 2017

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@unavatar/corepoints to another repo — not scored3.45.243,9621873 days agoavatardomainemailgithubgravatarinstagrammicrolinktelegramtwitteryoutube

Metrics by category

Vitality

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

93Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 3 days ago
24.2/36Commit cadence35/52 weeks with commits
18/18Commit volume525 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year525
human_commit_share
days_since_last_push3
active_weeks_last_year35

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 3 days ago
27/27Release cadencea release every ~1.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv3.45.24
releases_from_tagsno
days_since_latest_release3
mean_days_between_releases1.5
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?

62Moderate · 17% of overall
How it's scored
51.3/60Stars1,448 stars
16.1/25Forks86 forks
4.3/15Watchers7 watchers
Inputs used
forks86
stars1,448
watchers7
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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

65Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.7/22.5Commit distributiontop contributor authored 79% of commits
13.5/13.5Contributor breadth21 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled21
top_contributor_share0.792
How it's scored
40.8/42Issue resolution97% of issues closed
21.9/30PR acceptance409/561 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/20 approved changesets -- score normalized to 0
Inputs used
merged_prs409
open_issues2
closed_issues69
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.972
closed_unmerged_prs152
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
18.4/25Owner reach364 followers of microlinkhq
25/25Track record62 public repos, account ~9 yr old
Inputs used
followers364
owner_typeOrganization
is_verified
owner_loginmicrolinkhq
public_repos62
account_age_days3,306
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

83Excellent · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests10 out of 11 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://unavatar.io
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicsavatar-service, avatar, avatar-placeholder, microservice
has_wikiyes
homepagehttps://unavatar.io
docs_sitehttps://unavatar.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

40Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.2/2.5CI-Tests10 out of 11 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/20 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 6 contributing companies or organizations
0/10Dangerous-Workflowdangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
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
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4
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.

24At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeHTML without a type-check config
55/55Manageable file sizes0/169 source files over 60KB
Inputs used
primary_languageHTML
largest_source_bytes12,984
source_files_sampled169
oversized_source_files0

Key facts

1,448GitHub stars
21contributors
525commits, last 12 months
3days since last push
100releases
1bus factor
2open issues
npmpackage ecosystems

Data collection warnings

  • npm package '@unavatar/core' points at a different repository (https://github.com/Kikobeats/unavatar); excluded from ecosystem scoring

More detail

OpenSSF Scorecard 4.0 / 10
4.0aggregate

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-07-19 15:49 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
9CI-Tests10 out of 11 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/20 approved changesets -- score normalized to 0
10Contributorsproject has 6 contributing companies or organizations
0Dangerous-Workflowdangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 34
RegistryPackageVersion constraintManifest
npm@keyvhq/compress~2.2.0package.json
npm@keyvhq/core~2.1.15package.json
npm@keyvhq/memoize~2.2.1package.json
npm@keyvhq/multi~2.1.15package.json
npm@keyvhq/offline~2.2.0package.json
npm@keyvhq/redis~2.2.3package.json
npm@metascraper/helpers~5.51.1package.json
npm@microlink/mql~0.17.0package.json
npm@microlink/ping-url~1.4.16package.json
npmbrowserless~13.6.0package.json
npmcacheable-lookup~6.1.0package.json
npmdata-uri-regex~0.1.4package.json
npmdebug-logfmt~1.4.10package.json
npmgot~11.8.6package.json
npmhtml-get~2.26.0package.json
npmhttps-tls~1.0.24package.json
npmipaddr.js~2.4.0package.json
npmis-absolute-url~3.0.3package.json
npmis-antibot~2.2.0package.json
npmis-email-like~1.0.0package.json
npmlodash~4.18.1package.json
npmms~2.1.3package.json
npmp-any~3.0.0package.json
npmp-timeout~4.1.0package.json
npmpuppeteer~25.3.0package.json
npmre2~1.26.0package.json
npmsrcset~4.0.0package.json
npmstable-regex~1.0.1package.json
npmtangerine~2.1.3package.json
npmtop-crawler-agents~1.0.35package.json
npmtop-user-agents~2.1.105package.json
npmua-hints~1.0.1package.json
npmunique-random-array~2.0.0package.json
npmurl-regex-safe~4.0.0package.json
All dependencies 52

Full resolved dependency set from the GitHub dependency graph: 34 direct and 18 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npm@keyvhq/compress~2.2.0direct
npm@keyvhq/core~2.1.15direct
npm@keyvhq/memoize~2.2.1direct
npm@keyvhq/multi~2.1.15direct
npm@keyvhq/offline~2.2.0direct
npm@keyvhq/redis~2.2.3direct
npm@metascraper/helpers~5.51.1direct
npm@microlink/mql~0.17.0direct
npm@microlink/ping-url~1.4.16direct
npmbrowserless~13.6.0direct
npmcacheable-lookup~6.1.0direct
npmdata-uri-regex~0.1.4direct
npmdebug-logfmt~1.4.10direct
npmgot~11.8.6direct
npmhtml-get~2.26.0direct
npmhttps-tls~1.0.24direct
npmipaddr.js~2.4.0direct
npmis-absolute-url~3.0.3direct
npmis-antibot~2.2.0direct
npmis-email-like~1.0.0direct
npmlodash~4.18.1direct
npmms~2.1.3direct
npmp-any~3.0.0direct
npmp-timeout~4.1.0direct
npmpuppeteer~25.3.0direct
npmre2~1.26.0direct
npmsrcset~4.0.0direct
npmstable-regex~1.0.1direct
npmtangerine~2.1.3direct
npmtop-crawler-agents~1.0.35direct
npmtop-user-agents~2.1.105direct
npmua-hints~1.0.1direct
npmunique-random-array~2.0.0direct
npmurl-regex-safe~4.0.0direct
npm@commitlint/clilatestindirect
npm@commitlint/config-conventionallatestindirect
npmava7indirect
npmc8latestindirect
npmcheeriolatestindirect
npmci-publishlatestindirect
npmconventional-changelog-clilatestindirect
npmfinepacklatestindirect
npmgit-authors-clilatestindirect
npmgithub-generate-releaselatestindirect
npmmrilatestindirect
npmnano-stagedlatestindirect
npmproxyquirelatestindirect
npmsimple-git-hookslatestindirect
npmsinonlatestindirect
npmstandardlatestindirect
npmstandard-versionlatestindirect
npmterm-imglatestindirect
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.15.0 — full methodology · metrics wiki.

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