Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-15 14:53 UTC

jbboehr / dnsbl.php

DNSBL Lookup

PHPNo license detected★ 10 stars⑂ 3 forkssince Jan 2015View on GitHub ↗

jbboehr/dnsbl.php holds a health index of 33 out of 100, placing it in the At Risk band. It scores highest on Engineering Quality (59/100) and lowest on Vitality (21/100). It was last updated 212 days ago. A single contributor accounts for most of its recent work.

33
overall / 100
At Risk

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.

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

Ownership

John BoehrPersonal account
46 followers98 public repossince Mar 2010

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistjbboehr/dnsblv0.2.04,3462265 days agodnsbl

Metrics by category

Vitality

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

21At Risk · 21% of overall
How it's scored
3.6/36Push recencylast push 212 days ago
0.7/36Commit cadence1/52 weeks with commits
2.7/18Commit volume1 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year1
human_commit_share
days_since_last_push212
active_weeks_last_year1
How it's scored
16.2/27Ships releases2 version tags (no GitHub releases)
16.2/36Release recencylatest release 265 days ago
5.4/27Release cadencea release every ~3,920.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count2
latest_release_tagv0.2.0
releases_from_tagsyes
days_since_latest_release265
mean_days_between_releases3,920.6
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?

28At Risk · 17% of overall
How it's scored
15.5/60Stars10 stars
2.5/25Forks3 forks
0/15Watchers1 watchers
Inputs used
forks3
stars10
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
48.5/80Monthly downloads4,346 downloads/month across packagist
2/20Registry dependents1 packages depend on it
Inputs used
packagesjbboehr/dnsbl
dependents1
ecosystemspackagist
total_downloads375,708
monthly_downloads4,346
unverified_packages_excluded

Sustainability & Governance

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

54Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1.1/22.5Commit distributiontop contributor authored 95% of commits
2.7/13.5Contributor breadth2 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.952
How it's scored
42/42Issue resolution100% of issues closed
21.4/30PR acceptance5/7 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/20 approved changesets -- score normalized to 0
Inputs used
merged_prs5
open_issues0
closed_issues3
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs2
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
12/25Owner reach46 followers of jbboehr
25/25Track record98 public repos, account ~16 yr old
Inputs used
followers46
owner_typeUser
is_verified
owner_loginjbboehr
public_repos98
account_age_days5,962
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on packagist
26/35Publish recencylatest publish 265 days ago
12/20Version history2 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesjbboehr/dnsbl
ecosystemspackagist
any_deprecatedno
min_days_since_publish265

Engineering Quality

Are baseline engineering and documentation practices in place?

59Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests1 out of 5 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics2 topics
10/10Wiki
Inputs used
topicsdnsbl, php
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

24At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0.5/2.5CI-Tests1 out of 5 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 1/20 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesno data
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-Permissionsno data
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2.4
Excluded from scoring (no data or not applicable): 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.

30At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentNix, lockfile
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixyes
has_testsyes
lockfilescomposer.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
45.8/55Manageable file sizes1/6 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes135,627
source_files_sampled6
oversized_source_files1

Key facts

10GitHub stars
2contributors
1commits, last 12 months
212days since last push
2releases
1bus factor
0open issues
Packagistpackage ecosystems

More detail

OpenSSF Scorecard 2.4 / 10
2.4aggregate

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-07-15 14:53 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
2CI-Tests1 out of 5 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/20 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
9Vulnerabilities1 existing vulnerabilities detected
All dependencies 32

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

RegistryPackageVersionRelation
Packagistdoctrine/instantiator1.5.0indirect
Packagistmyclabs/deep-copy1.13.4indirect
Packagistnikic/php-parser5.6.2indirect
Packagistphar-io/manifest2.0.4indirect
Packagistphar-io/version3.2.1indirect
Packagistphpstan/phpstan1.12.32indirect
Packagistphpstan/phpstan-phpunit1.4.2indirect
Packagistphpstan/phpstan-strict-rules1.6.2indirect
Packagistphpunit/php-code-coverage9.2.32indirect
Packagistphpunit/php-file-iterator3.0.6indirect
Packagistphpunit/php-invoker3.1.1indirect
Packagistphpunit/php-text-template2.0.4indirect
Packagistphpunit/php-timer5.0.3indirect
Packagistphpunit/phpunit9.6.29indirect
Packagistsebastian/cli-parser1.0.2indirect
Packagistsebastian/code-unit1.0.8indirect
Packagistsebastian/code-unit-reverse-lookup2.0.3indirect
Packagistsebastian/comparator4.0.9indirect
Packagistsebastian/complexity2.0.3indirect
Packagistsebastian/diff4.0.6indirect
Packagistsebastian/environment5.1.5indirect
Packagistsebastian/exporter4.0.8indirect
Packagistsebastian/global-state5.0.8indirect
Packagistsebastian/lines-of-code1.0.4indirect
Packagistsebastian/object-enumerator4.0.4indirect
Packagistsebastian/object-reflector2.0.4indirect
Packagistsebastian/recursion-context4.0.6indirect
Packagistsebastian/resource-operations3.0.4indirect
Packagistsebastian/type3.2.1indirect
Packagistsebastian/version3.0.2indirect
Packagistsquizlabs/php_codesniffer3.13.4indirect
Packagisttheseer/tokenizer1.2.3indirect
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.11.0 — full methodology · metrics wiki.

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