Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-15 23:48 UTC

FriendsOfFlarum / polls

A Flarum extension that adds polls to your discussions

PHP · TypeScriptMIT★ 26 stars⑂ 18 forkssince Jul 2019View on GitHub ↗

FriendsOfFlarum/polls holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (84/100) and lowest on Community & Adoption (49/100). It was last updated 1 day ago. 3 contributors account 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

Friends of FlarumOrganization · verified domain
107 followers114 public repossince Sep 2018

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistfof/polls3.0.110,4289929 days agoflarum

Metrics by category

Vitality

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

82Excellent · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
9/36Commit cadence — 13/52 weeks with commits
14.7/18Commit volume — 42 commits in the last year
10/10OpenSSF Scorecard: Maintained — 20 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year42
human_commit_share1
days_since_last_push1
active_weeks_last_year13

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 61 releases published
36/36Release recency — latest release 4 days ago
27/27Release cadence — a release every ~12.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count61
latest_release_tag2.3.7
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases12.3
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?

49Weak · 17% of overall
How it's scored
22.7/60Stars — 26 stars
10.3/25Forks — 18 forks
1.7/15Watchers — 3 watchers
Inputs used
forks18
stars26
watchers3
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
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
53.6/80Monthly downloads — 10,428 downloads/month across packagist
7.6/20Registry dependents — 13 packages depend on it
Inputs used
packagesfof/polls
dependents13
ecosystemspackagist
total_downloads158,250
monthly_downloads10,428
unverified_packages_excluded—

Sustainability & Governance

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

84Excellent · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
17.8/22.5Commit distribution — top contributor authored 21% of commits
13.5/13.5Contributor breadth — 28 contributors
10/10OpenSSF Scorecard: Contributors — project has 20 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled28
top_contributor_share0.211
How it's scored
33.4/42Issue resolution — 80% of issues closed
22.7/30PR acceptance — 81/107 decided PRs merged
13/13Newcomer PR acceptance — 2/2 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-Review — Found 7/30 approved changesets -- score normalized to 2
Inputs used
merged_prs81
open_issues10
closed_issues39
prs_merged_7d1
prs_decided_7d1
prs_merged_30d5
prs_decided_30d6
issue_closed_ratio0.796
closed_unmerged_prs26
first_time_authors_30d2
first_time_prs_merged_30d2
first_time_prs_decided_30d2
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
14.6/25Owner reach — 107 followers of FriendsOfFlarum
25/25Track record — 114 public repos, account ~8 yr old
Inputs used
followers107
owner_typeOrganization
is_verifiedyes
owner_loginFriendsOfFlarum
public_repos114
account_age_days2,981

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

75Good · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — js/package.json ("prettier"), phpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 20 out of 21 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://discuss.flarum.org/d/20586
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttps://discuss.flarum.org/d/20586
docs_sitehttps://discuss.flarum.org/d/20586
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

74Good · 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/2.5CI-Tests — 20 out of 21 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 7/30 approved changesets -- score normalized to 2
2.5/2.5Contributors — project has 20 contributing companies or organizations
0/10Dangerous-Workflow — no data
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 — 20 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
4/5SAST — SAST tool is not run on all commits -- score normalized to 8
5/5Security-Policy — security policy file 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_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate6.8
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages15
unassessed_packages5
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 15 resolved dependencies against OSV. 5 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

61Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
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
llms_txt_url—
legible_history_share0.85
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — js/package.json ("prettier"), phpstan.neon
11/11Static type checking — js/tsconfig.json
10/10Reproducible environment — lockfile
8/10Demonstrated agent practice — 4 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsjs/tsconfig.json
agent_commit_share0.04
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
27/45Type-checkable code — PHP with type-check config (js/tsconfig.json)
55/55Manageable file sizes — 0/272 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes37,600
source_files_sampled272
oversized_source_files0

Key facts

26GitHub stars
28contributors
42commits, last 12 months
1days since last push
61releases
3bus factor
10open issues
npm, Packagistpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 18 ⇿
0Stars
18Forks
60Releases

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.

0481216201822019-072023-032026-11
Major 3Minor 9Patch 39

Each point covers 7 days.

OpenSSF Scorecard 6.8 / 10
6.8aggregate

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-11-15 23:47 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
9CI-Tests20 out of 21 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 7/30 approved changesets -- score normalized to 2
10Contributorsproject has 20 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained20 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
8SASTSAST tool is not run on all commits -- score normalized to 8
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
Packagistflarum/core^2.0.0composer.json
All dependencies 20

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

RegistryPackageVersionRelation
Packagistflarum/core—direct
npm@pnpm/exe.android-arm6412.10.1indirect
npm@pnpm/exe.android-x6412.10.1indirect
npm@pnpm/exe.darwin-arm6412.10.1indirect
npm@pnpm/exe.darwin-x6412.10.1indirect
npm@pnpm/exe.freebsd-x6412.10.1indirect
npm@pnpm/exe.linux-arm6412.10.1indirect
npm@pnpm/exe.linux-arm64-musl12.10.1indirect
npm@pnpm/exe.linux-ppc6412.10.1indirect
npm@pnpm/exe.linux-riscv6412.10.1indirect
npm@pnpm/exe.linux-s390x12.10.1indirect
npm@pnpm/exe.linux-x6412.10.1indirect
npm@pnpm/exe.linux-x64-musl12.10.1indirect
npm@pnpm/exe.win32-arm6412.10.1indirect
npm@pnpm/exe.win32-x6412.10.1indirect
npmpnpm12.10.1indirect
Packagistflarum/audit—indirect
Packagistflarum/phpstan—indirect
Packagistflarum/tags—indirect
Packagistflarum/testing—indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 15 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 5 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

No known advisories affect the assessed dependencies.

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