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

shlinkio / shlink-test-utils

Provides convenient tools and helpers to run different kind of tests on shlink project

PHPMIT★ 1 star⑂ 1 forksince Aug 2019View on GitHub ↗
KindCommand-line toolhow this is determined

shlinkio/shlink-test-utils holds a health index of 47 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (68/100) and lowest on AI Readiness (20/100). It was last updated 47 days ago. A single contributor accounts for most of its recent work.

47
overall / 100
Weak

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.

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

Ownership

shlinkioOrganization · verified domain
95 followers36 public repossince Jul 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagistshlinkio/shlink-test-utilsv4.6.04,4393995 days ago

Metrics by category

Vitality

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

53Moderate · 21% of overall
How it's scored
18/36Push recency — last push 47 days ago
4.2/36Commit cadence — 6/52 weeks with commits
10.3/18Commit volume — 13 commits in the last year
1/10OpenSSF Scorecard: Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year13
human_commit_share1
days_since_last_push47
active_weeks_last_year6
How it's scored
27/27Ships releases — 39 releases published
27/36Release recency — latest release 95 days ago
19.8/27Release cadence — a release every ~93.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count39
latest_release_tagv4.6.0
releases_from_tagsno
days_since_latest_release95
mean_days_between_releases93.7
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?

36Weak · 17% of overall
How it's scored
0/60Stars — 1 stars
0/25Forks — 1 forks
0/15Watchers — 1 watchers
Inputs used
forks1
stars1
watchers1
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
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
48.6/80Monthly downloads — 4,439 downloads/month across packagist
2/20Registry dependents — 1 packages depend on it
Inputs used
packagesshlinkio/shlink-test-utils
dependents1
ecosystemspackagist
total_downloads74,877
monthly_downloads4,439
unverified_packages_excluded—

Sustainability & Governance

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

68Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
42/42Issue resolution — 100% of issues closed
29.2/30PR acceptance — 38/39 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/16 approved changesets -- score normalized to 0
Inputs used
merged_prs38
open_issues0
closed_issues6
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs1
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
30/30Ownership backing — organization-owned
20/20Verified domain
14.3/25Owner reach — 95 followers of shlinkio
23.4/25Track record — 36 public repos, account ~10 yr old
Inputs used
followers95
owner_typeOrganization
is_verifiedyes
owner_loginshlinkio
public_repos36
account_age_days3,720

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 95 days ago
20/20Version history — 39 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesshlinkio/shlink-test-utils
ecosystemspackagist
any_deprecatedno
min_days_since_publish95

Engineering Quality

Are baseline engineering and documentation practices in place?

48Weak · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
6/20OpenSSF Scorecard: CI-Tests — 5 out of 13 merged PRs checked by a CI test -- score normalized to 3
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://shlink.io
10/10Repository description
10/10Topics — 1 topics
10/10Wiki
Inputs used
topicshacktoberfest
has_wikiyes
homepage—
docs_sitehttps://shlink.io
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

32At Risk · 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
0.8/2.5CI-Tests — 5 out of 13 merged PRs checked by a CI test -- score normalized to 3
0/2.5CII-Best-Practices — no data
0/7.5Code-Review — Found 0/16 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0.8/7.5Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
0/5Packaging — no data
0/5Pinned-Dependencies — no data
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 — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate3.2
Excluded from scoring (no data or not applicable): CII-Best-Practices, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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.

20At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
13.9/40Legible commit history — 26 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.26
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — PHP without a type-check config
55/55Manageable file sizes — 0/10 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes3,316
source_files_sampled10
oversized_source_files0

Key facts

1GitHub stars
1contributors
13commits, last 12 months
47days since last push
39releases
1bus factor
0open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

OpenSSF Scorecard 3.2 / 10
3.2aggregate

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-14 13:50 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
3CI-Tests5 out of 13 merged PRs checked by a CI test -- score normalized to 3
n/aCII-Best-Practicesinternal error: error during http.Do: Get "https://www.bestpractices.dev/projects.json?url=https://github.com/shlinkio/shlink-test-utils": Get "https://www.bestpractices.dev/projects.json?url=https://github.com/shlinkio/shlink-test-utils": dial tcp: lookup www.bestpractices.dev on 127.0.0.11:53: server misbehaving
0Code-ReviewFound 0/16 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
1Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
Packagistdoctrine/data-fixtures^1.8composer.json
Packagistdoctrine/orm^3.6composer.json
Packagistfig/http-message-util^1.1composer.json
Packagistguzzlehttp/guzzle^7.11composer.json
Packagistpsr/container^2.0composer.json
Packagistpsr/http-server-middleware^1.0composer.json
Packagistshlinkio/shlink-json^1.2composer.json
Packagistsymfony/console^8.0composer.json
Packagistsymfony/event-dispatcher^8.0composer.json
Packagistsymfony/process^8.0composer.json
All dependencies 15

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

RegistryPackageVersionRelation
Packagistdoctrine/data-fixtures—direct
Packagistdoctrine/orm—direct
Packagistfig/http-message-util—direct
Packagistguzzlehttp/guzzle—direct
Packagistpsr/container—direct
Packagistpsr/http-server-middleware—direct
Packagistshlinkio/shlink-json—direct
Packagistsymfony/console—direct
Packagistsymfony/event-dispatcher—direct
Packagistsymfony/process—direct
Packagistcarthage-software/mago—indirect
Packagistphp—indirect
Packagistphpunit/php-code-coverage—indirect
Packagistphpunit/phpunit—indirect
Packagistshlinkio/shlink-mago-config—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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 — Packagist.