Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-22 18:35 UTC

blisspixel / recon

Public-metadata domain intelligence from DNS, certificate transparency, and unauthenticated identity discovery. Local Python CLI, versioned JSON, and stdio MCP server. No credentials or active scanning.

PythonApache-2.0★ 4 stars⑂ 0 forkssince Apr 2026View on GitHub ↗
KindCommand-line toolMCP serverLibraryhow this is determined

blisspixel/recon holds a health index of 88 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (100/100) and lowest on Sustainability & Governance (50/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Nick SealPersonal account
6 followers14 public repossince Oct 2017

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
PyPIrecon-tool2.17.106,5862400 days agodnsdomain-intelligencemcposintreconsaas-fingerprintingsecurity

Metrics by category

Vitality

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

86Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
13.2/36Commit cadence19/52 weeks with commits
18/18Commit volume1,033 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,033
human_commit_share1
days_since_last_push0
active_weeks_last_year19

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~0.2 days
10/10OpenSSF Scorecard: Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
Inputs used
releases_count100
latest_release_tagv2.17.10
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases0.2

Community & Adoption

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

51Moderate · 17% of overall
How it's scored
7.7/60Stars4 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars4
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
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_servicesapi.securityscorecards.dev, github.com, shields.io
has_pull_request_templateyes
How it's scored
50.9/80Monthly downloads6,586 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesrecon-tool
dependents
ecosystemspypi
total_downloads
monthly_downloads6,586
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

50Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolutionno issues or no data
27.9/30PR acceptance133/143 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs133
open_issues0
closed_issues0
prs_merged_7d22
prs_decided_7d22
prs_merged_30d60
prs_decided_30d60
issue_closed_ratio
closed_unmerged_prs10
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
6.1/25Owner reach6 followers of blisspixel
20.6/25Track record14 public repos, account ~8 yr old
Inputs used
followers6
owner_typeUser
is_verified
owner_loginblisspixel
public_repos14
account_age_days3,237
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 0 days ago
20/20Version history240 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesrecon-tool
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

100Exceptional · 19% of overall

Engineering practices

100Exceptional
How it's scored
24/24CI workflows8 workflow(s)
24/24Tests present
16/16Linter configpyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests14 out of 14 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://pypi.org/project/recon-tool/
10/10Repository description
10/10Topics13 topics
10/10Wiki
Inputs used
topicsdomain-intelligence, email-security, mcp, osint, passive-recon, recon, reconnaissance, certificate-transparency, dns, mcp-server, public-metadata, python, saas-fingerprinting
has_wikiyes
homepagehttps://pypi.org/project/recon-tool/
docs_sitehttps://pypi.org/project/recon-tool/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

86Excellent · 16% of overall

Security posture

83Excellent
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
2.5/2.5CI-Tests14 out of 14 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
5/5Fuzzingproject is fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
5/5Pinned-Dependenciesall dependencies are pinned
5/5SASTSAST tool is run on all commits
5/5Security-Policysecurity policy file detected
7.5/7.5Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate8.3

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages116
unassessed_packages0
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 116 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.

80Excellent · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history82 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.82
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes20,374
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configpyproject.toml ([tool.ruff])
11/11Static type checkingsrc/recon_tool/py.typed
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configssrc/recon_tool/py.typed
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
27/45Type-checkable codePython with type-check config (src/recon_tool/py.typed)
54.8/55Manageable file sizes2/620 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes71,086
source_files_sampled620
oversized_source_files2
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
20/20MCP server
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalyes
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

4GitHub stars
1contributors
1,033commits, last 12 months
0days since last push
100releases
1bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index pypi:recon-tool@2.17.10; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 8.3 / 10
8.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-08-22 18:34 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests14 out of 14 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
10Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
PyPItyper>=0.24.1pyproject.toml
PyPIrich>=13.0pyproject.toml
PyPIhttpx>=0.27pyproject.toml
PyPIdnspython>=2.6pyproject.toml
PyPIpyyaml>=6.0pyproject.toml
PyPIdefusedxml>=0.7pyproject.toml
PyPImcp>=2.0.0,<3pyproject.toml
PyPInetworkx>=3.0pyproject.toml
PyPIpublicsuffixlist>=1.0pyproject.toml
PyPIdeal>=4.24.0pyproject.toml
PyPIpython-multipart>=0.0.27pyproject.toml
All dependencies 116

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

RegistryPackageVersionRelation
PyPIdeal4.24.6direct
PyPIdefusedxml0.7.1direct
PyPIdnspython2.8.0direct
PyPIhttpx0.28.1direct
PyPImcp2.0.0direct
PyPInetworkx3.6.1direct
PyPIpublicsuffixlist1.0.2.20260726direct
PyPIpython-multipart0.0.32direct
PyPIpyyaml6.0.3direct
PyPIrich15.0.0direct
PyPItyper0.27.1direct
PyPIaiohappyeyeballs2.6.2indirect
PyPIaiohttp3.14.3indirect
PyPIaiosignal1.4.0indirect
PyPIannotated-doc0.0.4indirect
PyPIannotated-types0.7.0indirect
PyPIanthropic0.120.2indirect
PyPIanybadge1.16.0indirect
PyPIanyio4.14.1indirect
PyPIattrs26.1.0indirect
PyPIboolean-py5.0indirect
PyPIcachecontrol0.14.4indirect
PyPIcertifi2026.6.17indirect
PyPIcffi2.0.0indirect
PyPIcfgv3.5.0indirect
PyPIcharset-normalizer3.4.7indirect
PyPIclick8.4.2indirect
PyPIcolorama0.4.6indirect
PyPIcosmic-ray8.4.6indirect
PyPIcoverage7.14.3indirect
PyPIcryptography50.0.0indirect
PyPIcyclonedx-python-lib11.11.0indirect
PyPIdecorator5.3.1indirect
PyPIdistlib0.4.3indirect
PyPIdistro1.9.0indirect
PyPIdocstring-parser0.18.0indirect
PyPIexecnet2.1.2indirect
PyPIexit-codes1.3.0indirect
PyPIfilelock3.29.4indirect
PyPIfrozenlist1.8.0indirect
PyPIgitdb4.0.12indirect
PyPIgitpython3.1.59indirect
PyPIgreenlet3.5.3indirect
PyPIh110.16.0indirect
PyPIhatchling1.31.0indirect
PyPIhttpcore1.0.9indirect
PyPIhttpcore22.9.1indirect
PyPIhttpx22.9.1indirect
PyPIhypothesis6.165.5indirect
PyPIidentify2.6.19indirect
PyPIidna3.18indirect
PyPIiniconfig2.3.0indirect
PyPIjiter0.16.0indirect
PyPIjsonschema4.26.0indirect
PyPIjsonschema-specifications2025.9.1indirect
PyPIlicense-expression30.4.4indirect
PyPImarkdown-it-py4.2.0indirect
PyPImcp-types2.0.0indirect
PyPImdurl0.1.2indirect
PyPImsgpack1.2.1indirect
PyPImultidict6.7.1indirect
PyPInodeenv1.10.0indirect
PyPIopenai2.52.0indirect
PyPIopentelemetry-api1.44.0indirect
PyPIpackageurl-python0.17.6indirect
PyPIpackaging26.2indirect
PyPIparso0.8.7indirect
PyPIpathspec1.1.1indirect
PyPIpip26.2.1indirect
PyPIpip-api0.0.34indirect
PyPIpip-audit2.10.1indirect
PyPIpip-requirements-parser32.0.1indirect
PyPIplatformdirs4.10.0indirect
PyPIpluggy1.6.0indirect
PyPIpre-commit4.6.2indirect
PyPIpropcache0.5.2indirect
PyPIpy-serializable2.1.0indirect
PyPIpycparser3.0indirect
PyPIpydantic2.13.4indirect
PyPIpydantic-core2.46.4indirect
PyPIpygments2.20.0indirect
PyPIpyjwt2.13.0indirect
PyPIpyparsing3.3.2indirect
PyPIpyright1.1.411indirect
PyPIpytest9.1.1indirect
PyPIpytest-asyncio1.4.0indirect
PyPIpytest-cov7.1.0indirect
PyPIpytest-xdist3.8.0indirect
PyPIpython-discovery1.4.2indirect
PyPIpywin32312indirect
PyPIrecon-tool2.17.7indirect
PyPIreferencing0.37.0indirect
PyPIrequests2.34.2indirect
PyPIrpds-py2026.5.1indirect
PyPIruff0.16.2indirect
PyPIshellingham1.5.4indirect
PyPIsmmap5.0.3indirect
PyPIsniffio1.3.1indirect
PyPIsortedcontainers2.4.0indirect
PyPIsqlalchemy2.0.51indirect
PyPIsse-starlette3.4.5indirect
PyPIstarlette1.3.1indirect
PyPIstevedore5.8.0indirect
PyPItoml0.10.2indirect
PyPItomli2.4.1indirect
PyPItomli-w1.2.0indirect
PyPItqdm4.70.0indirect
PyPItrove-classifiers2026.6.1.19indirect
PyPItruststore0.10.4indirect
PyPItyping-extensions4.15.0indirect
PyPItyping-inspection0.4.2indirect
PyPIurllib32.7.0indirect
PyPIuvicorn0.49.0indirect
PyPIvirtualenv21.5.1indirect
PyPIyarl1.24.2indirect
PyPIyattag1.16.1indirect
Dependency advisories 0

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

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