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

digitaltitransversal / femsa-php

PHPMIT★ 5 stars⑂ 0 forkssince Feb 2024View on GitHub ↗

digitaltitransversal/femsa-php holds a health index of 62 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (77/100) and lowest on Community & Adoption (45/100). It was last updated 33 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

138 followers13 public repossince Jul 2022

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistdigitalfemsa/femsa-php1.2.13,084940 days agophprestapisdkfemsa

Metrics by category

Vitality

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

58Moderate · 21% of overall
How it's scored
18/36Push recencylast push 33 days ago
5.5/36Commit cadence8/52 weeks with commits
10.6/18Commit volume14 commits in the last year
1/10OpenSSF Scorecard: Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year14
human_commit_share1
days_since_last_push33
active_weeks_last_year8
How it's scored
27/27Ships releases11 releases published
36/36Release recencylatest release 40 days ago
19.8/27Release cadencea release every ~88.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count11
latest_release_tag1.2.1
releases_from_tagsno
days_since_latest_release40
mean_days_between_releases88.9
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?

45Weak · 17% of overall
How it's scored
9.8/60Stars5 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars5
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
46.5/80Monthly downloads3,084 downloads/month across packagist
0/20Registry dependents0 packages depend on it
Inputs used
packagesdigitalfemsa/femsa-php
dependents0
ecosystemspackagist
total_downloads49,095
monthly_downloads3,084
unverified_packages_excluded

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
25.2/54Bus factor2 contributor(s) cover half of all commits
13.3/22.5Commit distributiontop contributor authored 41% of commits
6.8/13.5Contributor breadth5 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor2
contributors_sampled5
top_contributor_share0.407
How it's scored
0/42Issue resolutionno issues or no data
5.5/30PR acceptance21/115 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-ReviewFound 13/24 approved changesets -- score normalized to 5
Inputs used
merged_prs21
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
closed_unmerged_prs94
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
15.4/25Owner reach138 followers of digitaltitransversal
16.6/25Track record13 public repos, account ~4 yr old
Inputs used
followers138
owner_typeOrganization
is_verifiedno
owner_logindigitaltitransversal
public_repos13
account_age_days1,512

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 40 days ago
20/20Version history9 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesdigitalfemsa/femsa-php
ecosystemspackagist
any_deprecatedno
min_days_since_publish40

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter config.php-cs-fixer.dist.php
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests13 out of 21 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://www.femsa.com/
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_sitehttps://www.femsa.com/
has_readmeyes
has_docs_diryes
has_descriptionno

Security

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

51Moderate · 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
1.5/2.5CI-Tests13 out of 21 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-ReviewFound 13/24 approved changesets -- score normalized to 5
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
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
0.8/7.5Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
0/5Packagingno data
1.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
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.7
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
13.1/35Direct dependencies free of known advisories2 affected: guzzlehttp/guzzle 6.5.8 (high 7.2), guzzlehttp/psr7 1.9.1 (moderate 5.3)
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
35.3/40No advisories left outstanding1 advisory-carrying package(s) unaddressed past 90 days; oldest published 95 days ago
Inputs used
sourceosv
advisories13
affected_packages2
assessed_packages59
unassessed_packages0
affected_by_severityhigh 1, moderate 1
direct_affected_packages2
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 59 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

56Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history22 of 28 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.786
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format config.php-cs-fixer.dist.php
0/11Static type checking
10/10Reproducible environmentdevcontainer, Dockerfile, lockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 28
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
3/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsyes
lockfilescomposer.lock
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontaineryes
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codePHP without a type-check config
50.9/55Manageable file sizes14/186 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes181,487
source_files_sampled186
oversized_source_files14

Key facts

5GitHub stars
5contributors
14commits, last 12 months
33days since last push
11releases
2bus factor
0open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

OpenSSF Scorecard 4.7 / 10
4.7aggregate

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 20:17 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
6CI-Tests13 out of 21 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 13/24 approved changesets -- score normalized to 5
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate 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
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
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 2
RegistryPackageVersion constraintManifest
Packagistguzzlehttp/guzzle^7.3composer.json
Packagistguzzlehttp/psr7^1.7 || ^2.0composer.json
All dependencies 59

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

RegistryPackageVersionRelation
Packagistguzzlehttp/guzzle6.5.8direct
Packagistguzzlehttp/psr71.9.1direct
Packagistcomposer/pcre3.1.4indirect
Packagistcomposer/semver3.4.4indirect
Packagistcomposer/xdebug-handler3.0.5indirect
Packagistdoctrine/annotations1.14.4indirect
Packagistdoctrine/deprecations1.1.6indirect
Packagistdoctrine/instantiator1.5.0indirect
Packagistdoctrine/lexer2.1.1indirect
Packagistfriendsofphp/php-cs-fixer3.9.5indirect
Packagistguzzlehttp/promises1.5.3indirect
Packagistmyclabs/deep-copy1.13.4indirect
Packagistphar-io/manifest2.0.4indirect
Packagistphar-io/version3.2.1indirect
Packagistphp-cs-fixer/diff2.0.2indirect
Packagistphpstan/phpstan1.10.47indirect
Packagistphpunit/php-code-coverage7.0.17indirect
Packagistphpunit/php-file-iterator2.0.6indirect
Packagistphpunit/php-text-template1.2.1indirect
Packagistphpunit/php-timer2.1.4indirect
Packagistphpunit/php-token-stream4.0.4indirect
Packagistphpunit/phpunit8.5.52indirect
Packagistpsr/cache3.0.0indirect
Packagistpsr/container2.0.2indirect
Packagistpsr/event-dispatcher1.0.0indirect
Packagistpsr/http-message1.1indirect
Packagistpsr/log3.0.2indirect
Packagistralouphie/getallheaders3.0.3indirect
Packagistsebastian/code-unit-reverse-lookup1.0.3indirect
Packagistsebastian/comparator3.0.7indirect
Packagistsebastian/diff3.0.6indirect
Packagistsebastian/environment4.2.5indirect
Packagistsebastian/exporter3.1.8indirect
Packagistsebastian/global-state3.0.6indirect
Packagistsebastian/object-enumerator3.0.5indirect
Packagistsebastian/object-reflector1.1.3indirect
Packagistsebastian/recursion-context3.0.3indirect
Packagistsebastian/resource-operations2.0.3indirect
Packagistsebastian/type1.1.5indirect
Packagistsebastian/version2.0.1indirect
Packagistsymfony/console6.4.39indirect
Packagistsymfony/deprecation-contracts3.7.0indirect
Packagistsymfony/event-dispatcher6.4.37indirect
Packagistsymfony/event-dispatcher-contracts3.7.0indirect
Packagistsymfony/filesystem6.4.39indirect
Packagistsymfony/finder6.4.34indirect
Packagistsymfony/options-resolver6.4.30indirect
Packagistsymfony/polyfill-ctype1.37.0indirect
Packagistsymfony/polyfill-intl-grapheme1.38.1indirect
Packagistsymfony/polyfill-intl-idn1.38.1indirect
Packagistsymfony/polyfill-intl-normalizer1.38.0indirect
Packagistsymfony/polyfill-mbstring1.38.1indirect
Packagistsymfony/polyfill-php801.37.0indirect
Packagistsymfony/polyfill-php811.38.1indirect
Packagistsymfony/process6.4.39indirect
Packagistsymfony/service-contracts3.7.0indirect
Packagistsymfony/stopwatch6.4.24indirect
Packagistsymfony/string7.4.11indirect
Packagisttheseer/tokenizer1.3.1indirect
Dependency advisories 2

This repository publishes no package the index resolves, so its own dependency graph was assessed — 59 packages, which also include development and test pins that never ship: 2 carry known advisories, of which 2 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
guzzlehttp/guzzle6.5.8directhigh98.0.1
guzzlehttp/psr71.9.1directmoderate42.12.3

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