Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 07:46 UTC

DedSecInside / TorBot

Dark Web OSINT Tool

PythonCustom license★ 4,726 stars⑂ 737 forkssince May 2017View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

DedSecInside/TorBot holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (84/100) and lowest on AI Readiness (44/100). It was last updated today. A single contributor accounts 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

DedSec InsideOrganization
248 followers10 public repossince Jul 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPItorbot4.3.0352730 days ago

Metrics by category

Vitality

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

71Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
6.2/36Commit cadence9/52 weeks with commits
16.2/18Commit volume63 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year63
human_commit_share0.81
days_since_last_push0
active_weeks_last_year9
How it's scored
27/27Ships releases14 releases published
36/36Release recencylatest release 30 days ago
12.6/27Release cadencea release every ~194.7 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count14
latest_release_tagv4.3.0
releases_from_tagsno
days_since_latest_release30
mean_days_between_releases194.7

Community & Adoption

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

81Excellent · 17% of overall
How it's scored
59.6/60Stars4,726 stars
23.9/25Forks737 forks
11.7/15Watchers127 watchers
Inputs used
forks737
stars4,726
watchers127
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
0/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_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes

Sustainability & Governance

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

66Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.8/22.5Commit distributiontop contributor authored 52% of commits
13.5/13.5Contributor breadth38 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled38
top_contributor_share0.518
How it's scored
40.2/42Issue resolution96% of issues closed
24.8/30PR acceptance218/264 decided PRs merged
0/13Newcomer PR acceptance0/2 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/8 approved changesets -- score normalized to 0
Inputs used
merged_prs218
open_issues5
closed_issues109
prs_merged_7d2
prs_decided_7d2
prs_merged_30d2
prs_decided_30d4
issue_closed_ratio0.956
closed_unmerged_prs46
first_time_authors_30d2
first_time_prs_merged_30d0
first_time_prs_decided_30d2
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
17.2/25Owner reach248 followers of DedSecInside
19.6/25Track record10 public repos, account ~10 yr old
Inputs used
followers248
owner_typeOrganization
is_verifiedno
owner_loginDedSecInside
public_repos10
account_age_days3,700

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 30 days ago
20/20Version history7 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagestorbot
ecosystemspypi
any_deprecatedno
min_days_since_publish30

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter config.flake8
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics20 topics
10/10Wiki
Inputs used
topicstor, tor-network, deepweb, dark-web, psnappz, crawler, spider, dedsec-inside, python-web-crawler, security-tools, security, python3, python, algorithm, osint, go, projects, hacking, torbot, hacktoberfest
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

71Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests13 out of 13 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/8 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 6 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
4.5/5SASTSAST tool is not run on all commits -- score normalized to 9
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.4
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages43
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:torbot@4.3.0 runtime dependency closure — what installing the published package pulls in — 43 packages. 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.

44Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
27/40Legible commit history41 of 81 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.506
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.flake8
0/11Static type checking
10/10Reproducible environmentDockerfile
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance19 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0.19
How it's scored
0/45Type-checkable codePython without a type-check config
55/55Manageable file sizes0/27 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes18,656
source_files_sampled27
oversized_source_files0

Key facts

4,726GitHub stars
38contributors
63commits, last 12 months
0days since last push
14releases
1bus factor
5open issues
PyPIpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 737 ⇿
0Stars
737Forks
13Releases

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.

0125250375500625750718192017-072022-022026-08
Major 2Minor 4Patch 5

Each point covers 9 days.

OpenSSF Scorecard 6.4 / 10
6.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-08-28 07:46 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests13 out of 13 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/8 approved changesets -- score normalized to 0
10Contributorsproject has 6 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 2 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
9SASTSAST tool is not run on all commits -- score normalized to 9
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 32
RegistryPackageVersion constraintManifest
PyPIaltgraph>=0.17.4pyproject.toml
PyPIbeautifulsoup4>=4.12.3pyproject.toml
PyPIcertifi>=2024.7.4pyproject.toml
PyPIcharset-normalizer>=3.3.2pyproject.toml
PyPIdecorator>=5.1.1pyproject.toml
PyPIidna>=3.15pyproject.toml
PyPIigraph>=0.11.4pyproject.toml
PyPIjoblib>=1.4.2pyproject.toml
PyPImacholib>=1.16.3pyproject.toml
PyPIprogress>=1.6pyproject.toml
PyPIpyinstaller>=6.8.0pyproject.toml
PyPIpyinstaller-hooks-contrib>=2024.6pyproject.toml
PyPIPySocks>=1.7.1pyproject.toml
PyPIpython-dotenv>=1.2.2pyproject.toml
PyPIscikit-learn>=1.5.0pyproject.toml
PyPIscipy>=1.13.0pyproject.toml
PyPIsix>=1.16.0pyproject.toml
PyPIsoupsieve>=2.8.4pyproject.toml
PyPItermcolor>=2.4.0pyproject.toml
PyPItexttable>=1.7.0pyproject.toml
PyPIthreadpoolctl>=3.5.0pyproject.toml
PyPIurllib3>=2.7.0pyproject.toml
PyPIvalidators>=0.22.0pyproject.toml
PyPItreelib>=1.7.1pyproject.toml
PyPInumpy>=1.26.4pyproject.toml
PyPIunipath>=1.1pyproject.toml
PyPIhttpx>=0.27.0pyproject.toml
PyPItabulate>=0.9.0pyproject.toml
PyPIphonenumbers>=8.13.37pyproject.toml
PyPIpytest>=9.0.3pyproject.toml
PyPIyattag>=1.15.2pyproject.toml
PyPItoml>=0.10.2pyproject.toml
All dependencies 77

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

RegistryPackageVersionRelation
PyPIaltgraphdirect
PyPIaltgraph0.17.4direct
PyPIbeautifulsoup4direct
PyPIbeautifulsoup44.12.3direct
PyPIcertifidirect
PyPIcertifi2024.7.4direct
PyPIcharset-normalizerdirect
PyPIcharset-normalizer3.3.2direct
PyPIdecoratordirect
PyPIdecorator5.1.1direct
PyPIhttpxdirect
PyPIhttpx0.27.0direct
PyPIidnadirect
PyPIidna3.15direct
PyPIigraphdirect
PyPIigraph0.11.4direct
PyPIjoblibdirect
PyPIjoblib1.4.2direct
PyPImacholibdirect
PyPImacholib1.16.3direct
PyPInumpydirect
PyPInumpy1.26.4direct
PyPIphonenumbersdirect
PyPIphonenumbers8.13.37direct
PyPIprogressdirect
PyPIprogress1.6direct
PyPIpyinstallerdirect
PyPIpyinstaller6.8.0direct
PyPIpyinstaller-hooks-contribdirect
PyPIpyinstaller-hooks-contrib2024.6direct
PyPIpysocksdirect
PyPIpysocks1.7.1direct
PyPIpytestdirect
PyPIpytest9.0.3direct
PyPIpython-dotenvdirect
PyPIpython-dotenv1.2.2direct
PyPIscikit-learndirect
PyPIscikit-learn1.5.0direct
PyPIscipydirect
PyPIscipy1.13.0direct
PyPIsixdirect
PyPIsix1.16.0direct
PyPIsoupsievedirect
PyPIsoupsieve2.8.4direct
PyPItabulatedirect
PyPItabulate0.9.0direct
PyPItermcolordirect
PyPItermcolor2.4.0direct
PyPItexttabledirect
PyPItexttable1.7.0direct
PyPIthreadpoolctldirect
PyPIthreadpoolctl3.5.0direct
PyPItomldirect
PyPItoml0.10.2direct
PyPItreelibdirect
PyPItreelib1.7.1direct
PyPIunipathdirect
PyPIunipath1.1direct
PyPIurllib3direct
PyPIurllib32.7.0direct
PyPIvalidatorsdirect
PyPIvalidators0.22.0direct
PyPIyattagdirect
PyPIyattag1.15.2direct
PyPIanyio4.3.0indirect
PyPIcolorama0.4.6indirect
PyPIh110.16.0indirect
PyPIhttpcore1.0.9indirect
PyPIiniconfig2.0.0indirect
PyPIpackaging24.0indirect
PyPIpefile2023.2.7indirect
PyPIpluggy1.5.0indirect
PyPIpywin32-ctypes0.2.2indirect
PyPIsetuptools83.0.0indirect
PyPIsniffio1.3.1indirect
PyPIsocksio1.0.0indirect
PyPItomli2.0.1indirect
Dependency advisories 0

Installing pypi:torbot@4.3.0 pulls in 43 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

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.