Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-11 14:11 UTC

microlinkhq / unavatar

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

HTMLMIT★ 1,463 stars⑂ 87 forkssince Apr 2018View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

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

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

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

Ownership

microlink.ioOrganization · verified domain
369 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.48.83,5982164 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 recency — last push 4 days ago
23.5/36Commit cadence — 34/52 weeks with commits
18/18Commit volume — 538 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year538
human_commit_share0.66
days_since_last_push4
active_weeks_last_year34

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 4 days ago
27/27Release cadence — a release every ~0.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv3.48.8
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases0.8
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/60Stars — 1,463 stars
16.1/25Forks — 87 forks
4.3/15Watchers — 7 watchers
Inputs used
forks87
stars1,463
watchers7
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges0
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?

61Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.6/22.5Commit distribution — top contributor authored 97% of commits
13.5/13.5Contributor breadth — 18 contributors
10/10OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled18
top_contributor_share0.972
How it's scored
40.8/42Issue resolution — 97% of issues closed
22.1/30PR acceptance — 440/596 decided PRs merged
0/13Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/22 approved changesets -- score normalized to 0
Inputs used
merged_prs440
open_issues2
closed_issues69
prs_merged_7d0
prs_decided_7d0
prs_merged_30d4
prs_decided_30d6
issue_closed_ratio0.972
closed_unmerged_prs156
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
18.5/25Owner reach — 369 followers of microlinkhq
25/25Track record — 62 public repos, account ~9 yr old
Inputs used
followers369
owner_typeOrganization
is_verifiedyes
owner_loginmicrolinkhq
public_repos62
account_age_days3,360

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 12 out of 12 merged PRs checked by a CI test -- score normalized to 10
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 site — https://unavatar.io
10/10Repository description
10/10Topics — 10 topics
10/10Wiki
Inputs used
topicsavatar, domain, email, github, gravatar, instagram, microlink, telegram, twitter, youtube
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?

47Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 12 out of 12 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/22 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 6 contributing companies or organizations
0/10Dangerous-Workflow — dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.1
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
7.2/25Indirect dependencies free of known advisories — 2 affected: ip 1.1.9 (high 8.1), private-ip 3.0.2 (high 8.2)
28.4/40No advisories left outstanding — 2 advisory-carrying package(s) unaddressed past 90 days; oldest published 830 days ago
Inputs used
sourceosv
advisories2
affected_packages2
assessed_packages369
unassessed_packages0
affected_by_severityhigh 2
direct_affected_packages0
Matched the npm:@unavatar/core@3.48.8 runtime dependency closure — what installing the published package pulls in — 369 packages. Reachability is not analyzed.

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.

48Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://unavatar.io/llms.txt)
40/40Legible commit history — 66 of 66 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://unavatar.io/llms.txt
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
10/10Demonstrated agent practice — 10 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 32 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency 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_share0.1
toolchain_manifests—
dependency_bot_commit_share0.32
How it's scored
0/45Type-checkable code — HTML without a type-check config
55/55Manageable file sizes — 0/176 source files over 60KB
Inputs used
primary_languageHTML
largest_source_bytes17,678
source_files_sampled176
oversized_source_files0

Key facts

1,463GitHub stars
18contributors
538commits, last 12 months
4days since last push
100releases
1bus factor
2open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • npm package '@unavatar/core' points at a different repository (https://github.com/Kikobeats/unavatar); excluded from ecosystem scoring

More detail

Star and fork history 0 ★ / 87 ⇿
0Stars
87Forks
88Releases

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.

0204060801008532018-042022-062026-08
Major 0Minor 21Patch 67

Each point covers 8 days.

OpenSSF Scorecard 4.1 / 10
4.1aggregate

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-11 14:11 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/22 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 1 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 35
RegistryPackageVersion constraintManifest
npm@keyvhq/compress~2.2.0package.json
npm@keyvhq/core~2.2.7package.json
npm@keyvhq/memoize~2.2.1package.json
npm@keyvhq/multi~2.2.6package.json
npm@keyvhq/offline~2.2.0package.json
npm@keyvhq/redis~2.2.3package.json
npm@metascraper/helpers~5.56.2package.json
npm@microlink/mql~0.19.0package.json
npm@microlink/ping-url~1.5.0package.json
npmbimi-url~1.0.0package.json
npmbrowserless~13.9.2package.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.27.0package.json
npmhttps-tls~1.0.24package.json
npmipaddr.js~2.5.0package.json
npmis-absolute-url~3.0.3package.json
npmis-antibot~2.5.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.10.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 54

Full resolved dependency set from the GitHub dependency graph: 35 direct and 19 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.2.7direct
npm@keyvhq/memoize~2.2.1direct
npm@keyvhq/multi~2.2.6direct
npm@keyvhq/offline~2.2.0direct
npm@keyvhq/redis~2.2.3direct
npm@metascraper/helpers~5.56.2direct
npm@microlink/mql~0.19.0direct
npm@microlink/ping-url~1.5.0direct
npmbimi-url~1.0.0direct
npmbrowserless~13.9.2direct
npmcacheable-lookup~6.1.0direct
npmdata-uri-regex~0.1.4direct
npmdebug-logfmt~1.4.10direct
npmgot~11.8.6direct
npmhtml-get~2.27.0direct
npmhttps-tls~1.0.24direct
npmipaddr.js~2.5.0direct
npmis-absolute-url~3.0.3direct
npmis-antibot~2.5.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.10.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-changeloglatestindirect
npmconventional-changelog-conventionalcommitslatestindirect
npmfinepacklatestindirect
npmgit-authors-clilatestindirect
npmgithub-generate-releaselatestindirect
npmmrilatestindirect
npmnano-stagedlatestindirect
npmproxyquirelatestindirect
npmsimple-git-hookslatestindirect
npmsinonlatestindirect
npmstandardlatestindirect
npmstandard-versionlatestindirect
npmterm-imglatestindirect
Dependency advisories 2

Installing npm:@unavatar/core@3.48.8 pulls in 369 packages, direct and transitive: 2 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
ip1.1.9indirecthigh1—
private-ip3.0.2indirecthigh1—

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.

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

How one result sits in the wider record: aggregate statistics — npm.