Public record
Software health reportschema 0.30.0 · metrics 2.5.0 · 2026-08-04 14:24 UTC

run-as-root / magento2-prometheus-exporter

Simple Magento 2 Prometheus Exporter.

PHPMIT★ 68 stars⑂ 23 forkssince Jun 2019View on GitHub ↗
KindPluginCommand-line toolhow this is determined

run-as-root/magento2-prometheus-exporter holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Vitality (78/100) and lowest on Community & Adoption (48/100). It was last updated today. A single contributor accounts for most of its recent work.

73
overall / 100
Good

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.

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

Ownership

run_as_root GmbHOrganization
50 followers31 public repossince Aug 2018

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

Metrics by category

Vitality

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

78Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
5.5/36Commit cadence — 8/52 weeks with commits
16.8/18Commit volume — 73 commits in the last year
10/10OpenSSF Scorecard: Maintained — 22 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year73
human_commit_share1
days_since_last_push0
active_weeks_last_year8
How it's scored
27/27Ships releases — 23 releases published
36/36Release recency — latest release 25 days ago
19.8/27Release cadence — a release every ~67.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count23
latest_release_tag4.2.2
releases_from_tagsno
days_since_latest_release25
mean_days_between_releases67.1
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?

48Weak · 17% of overall
How it's scored
29.6/60Stars — 68 stars
11.2/25Forks — 23 forks
5/15Watchers — 9 watchers
Inputs used
forks23
stars68
watchers9
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_badges1
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com
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
7.7/22.5Commit distribution — top contributor authored 66% of commits
13.5/13.5Contributor breadth — 19 contributors
10/10OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled19
top_contributor_share0.659
How it's scored
40.3/42Issue resolution — 96% of issues closed
28/30PR acceptance — 41/44 decided PRs merged
13/13Newcomer PR acceptance — 3/3 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 2/11 approved changesets -- score normalized to 1
Inputs used
merged_prs41
open_issues1
closed_issues24
prs_merged_7d0
prs_decided_7d0
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.96
closed_unmerged_prs3
first_time_authors_30d1
first_time_prs_merged_30d3
first_time_prs_decided_30d3
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
12.3/25Owner reach — 50 followers of run-as-root
23/25Track record — 31 public repos, account ~7 yr old
Inputs used
followers50
owner_typeOrganization
is_verified
owner_loginrun-as-root
public_repos31
account_age_days2,899

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — .php-cs-fixer.php, phpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 5 out of 6 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 10 topics
0/10Wiki
Inputs used
topicsmagento, magento2, prometheus-exporter, prometheus-metrics, magento2-module, magento2-extension, magento-extension, magento-module, prometheus, metrics
has_wikino
homepage
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

55Moderate · 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/2.5CI-Tests — 5 out of 6 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 2/11 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 6 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 22 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
1/5SAST — SAST tool is not run on all commits -- score normalized to 2
2/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.5
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.

55Moderate · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 85 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.85
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes6,380
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .php-cs-fixer.php, 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 — 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_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — PHP without a type-check config
55/55Manageable file sizes — 0/121 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes13,574
source_files_sampled121
oversized_source_files0

Key facts

68GitHub stars
19contributors
73commits, last 12 months
0days since last push
23releases
1bus factor
1open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch packagist package 'run_as_root/magento2-prometheus-exporter' from its registry
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 23 ⇿
0Stars
23Forks
15Releases

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.

048121620242322019-122022-102025-08
Major 1Minor 2Patch 12

Each point covers 6 days.

OpenSSF Scorecard 5.5 / 10
5.5aggregate

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-08-04 14:24 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
8CI-Tests5 out of 6 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 2/11 approved changesets -- score normalized to 1
10Contributorsproject has 6 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained22 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
2SASTSAST tool is not run on all commits -- score normalized to 2
4Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 19
RegistryPackageVersion constraintManifest
Packagistmagento/framework*composer.json
Packagistmagento/module-payment*composer.json
Packagistmagento/module-eav*composer.json
Packagistmagento/module-cron*composer.json
Packagistmagento/module-cms*composer.json
Packagistmagento/module-shipping*composer.json
Packagistmagento/module-catalog*composer.json
Packagistmagento/module-sales*composer.json
Packagistmagento/module-quote*composer.json
Packagistlaminas/laminas-http^2.15.0composer.json
Packagistmagento/module-config*composer.json
Packagistmagento/module-backend*composer.json
Packagistguzzlehttp/guzzle^7.4.5composer.json
Packagistsymfony/console^5.4.46|^6.0|^7.0composer.json
Packagistpsr/log^1.1|^2.0|^3.0composer.json
Packagistmonolog/monolog^2.9.0|^3.0composer.json
Packagistmagento/module-store*composer.json
Packagistmagento/module-indexer*composer.json
Packagistmagento/zend-db*composer.json
All dependencies 21

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

RegistryPackageVersionRelation
Packagistguzzlehttp/guzzledirect
Packagistlaminas/laminas-httpdirect
Packagistmagento/frameworkdirect
Packagistmagento/module-backenddirect
Packagistmagento/module-catalogdirect
Packagistmagento/module-cmsdirect
Packagistmagento/module-configdirect
Packagistmagento/module-crondirect
Packagistmagento/module-eavdirect
Packagistmagento/module-indexerdirect
Packagistmagento/module-paymentdirect
Packagistmagento/module-quotedirect
Packagistmagento/module-salesdirect
Packagistmagento/module-shippingdirect
Packagistmagento/module-storedirect
Packagistmagento/zend-dbdirect
Packagistmonolog/monologdirect
Packagistpsr/logdirect
Packagistsymfony/consoledirect
Packagistphpindirect
Packagistphpunit/phpunitindirect
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

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.5.0, schema v0.30.0 — full methodology · metrics wiki.

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