Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 13:59 UTC

nette / tracy

😎 Tracy: the addictive tool to ease debugging PHP code for cool developers. Friendly design, logging, profiler, advanced features like debugging AJAX calls or CLI support. You will love it.

PHPCustom license★ 1,838 stars⑂ 217 forkssince Nov 2012View on GitHub ↗

nette/tracy holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (87/100) and lowest on Security (43/100). It was last updated 23 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Nette FoundationOrganization · verified domain
253 followers43 public repossince Jun 2009

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagisttracy/tracyv2.12.1348,57010723 days agodebugxdebugprofilernettedebugger

Metrics by category

Vitality

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

79Good · 21% of overall
How it's scored
28.8/36Push recency — last push 23 days ago
19.4/36Commit cadence — 28/52 weeks with commits
18/18Commit volume — 107 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year107
human_commit_share1
days_since_last_push23
active_weeks_last_year28
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 23 days ago
19.8/27Release cadence — a release every ~93.4 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv2.12.1
releases_from_tagsno
days_since_latest_release23
mean_days_between_releases93.4

Community & Adoption

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

87Excellent · 17% of overall
How it's scored
52.9/60Stars — 1,838 stars
19.5/25Forks — 217 forks
10.2/15Watchers — 68 watchers
Inputs used
forks217
stars1,838
watchers68
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

86Excellent
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesci.appveyor.com, github.com, poser.pugx.org, shields.io
has_pull_request_templateyes
How it's scored
73.9/80Monthly downloads — 348,570 downloads/month across packagist
20/20Registry dependents — 1,476 packages depend on it
Inputs used
packagestracy/tracy
dependents1,476
ecosystemspackagist
total_downloads26,274,252
monthly_downloads348,570
unverified_packages_excluded—

Sustainability & Governance

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

69Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
2.6/22.5Commit distribution — top contributor authored 88% of commits
13.5/13.5Contributor breadth — 82 contributors
10/10OpenSSF Scorecard: Contributors — project has 35 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled82
top_contributor_share0.884
How it's scored
40.1/42Issue resolution — 96% of issues closed
15.9/30PR acceptance — 149/282 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs149
open_issues14
closed_issues295
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.955
closed_unmerged_prs133
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
17.3/25Owner reach — 253 followers of nette
24/25Track record — 43 public repos, account ~17 yr old
Inputs used
followers253
owner_typeOrganization
is_verifiedyes
owner_loginnette
public_repos43
account_age_days6,282

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 23 days ago
20/20Version history — 107 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagestracy/tracy
ecosystemspackagist
any_deprecatedno
min_days_since_publish23

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
16/16Linter config — eslint.config.js, phpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://tracy.nette.org
10/10Repository description
10/10Topics — 11 topics
0/10Wiki
Inputs used
topicsnette, nette-framework, tracy, dump-variables, php, debugger, profiler, ajax, php-errors, error-handling, dumper
has_wikino
homepagehttps://tracy.nette.org
docs_sitehttps://tracy.nette.org
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

43Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 35 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — no SAST tool detected
4.5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4.3
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, 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.

61Moderate · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://tracy.nette.org/llms.txt)
18.1/40Legible commit history — 34 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://tracy.nette.org/llms.txt
legible_history_share0.34
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes3,899
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js, phpstan.neon
0/11Static type checking
0/10Reproducible environment
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_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
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/69 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes23,765
source_files_sampled69
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
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

1,838GitHub stars
82contributors
107commits, last 12 months
23days since last push
100releases
1bus factor
14open issues
npm, 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

Star and fork history 0 ★ / 217 ⇿
0Stars
217Forks
99Releases

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.

0408012016020024021742013-032019-102026-05
Major 0Minor 10Patch 89

Each point covers 13 days.

OpenSSF Scorecard 4.3 / 10
4.3aggregate

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-10 13:59 UTC

10Binary-Artifactsno binaries found in the repo
1Branch-Protectionbranch protection is not maximal on development and all release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 35 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
9Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 15

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

RegistryPackageVersionRelation
npm@nette/eslint-plugin^0.2indirect
npmeslint^9.26.0indirect
Packagistext-json—indirect
Packagistext-session—indirect
Packagistlatte/latte—indirect
Packagistnette/di—indirect
Packagistnette/http—indirect
Packagistnette/mail—indirect
Packagistnette/phpstan-rules—indirect
Packagistnette/tester—indirect
Packagistnette/utils—indirect
Packagistphp—indirect
Packagistphpstan/extension-installer—indirect
Packagistphpstan/phpstan—indirect
Packagistpsr/log—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.