Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-25 01:51 UTC

GamehunterKaan / AutoPWN-Suite

AutoPWN Suite is a project for scanning vulnerabilities and exploiting systems automatically.

Python · JavaScriptApache-2.0★ 1,144 stars⑂ 147 forkssince May 2022View on GitHub ↗
KindCommand-line toolNetwork serviceLibraryhow this is determined

GamehunterKaan/AutoPWN-Suite holds a health index of 94 out of 100, placing it in the Exceptional band. It scores highest on Security (97/100) and lowest on Sustainability & Governance (68/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

94
overall / 100
Exceptional

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.

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

Ownership

Kaan GültekinPersonal account
150 followers20 public repossince Jul 2020

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
PyPIautopwn-suite2.8.1262241 day agosecuritypenetration-testingvulnerability-scannerexploitation

Metrics by category

Vitality

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

85Excellent · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
12.5/36Commit cadence — 18/52 weeks with commits
18/18Commit volume — 429 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year429
human_commit_share0.98
days_since_last_push1
active_weeks_last_year18

Release discipline

99Exceptional
How it's scored
27/27Ships releases — 41 releases published
36/36Release recency — latest release 1 days ago
27/27Release cadence — a release every ~11.4 days
9/10OpenSSF Scorecard: Signed-Releases — 5 out of the last 5 releases have a total of 8 signed artifacts.
Inputs used
releases_count41
latest_release_tagv2.8.1
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases11.4

Community & Adoption

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

70Good · 17% of overall
How it's scored
49.6/60Stars — 1,144 stars
18/25Forks — 147 forks
8/15Watchers — 29 watchers
Inputs used
forks147
stars1,144
watchers29
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges13
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesapi.securityscorecards.dev, github.com, shields.io, www.bestpractices.dev
has_pull_request_templateno
How it's scored
32.3/80Monthly downloads — 262 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesautopwn-suite
dependents—
ecosystemspypi
total_downloads—
monthly_downloads262
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?

68Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.6/22.5Commit distribution — top contributor authored 71% of commits
10.8/13.5Contributor breadth — 8 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled8
top_contributor_share0.706
How it's scored
42/42Issue resolution — 100% of issues closed
26.8/30PR acceptance — 34/38 decided PRs merged
13/13Newcomer PR acceptance — 2/2 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs34
open_issues0
closed_issues33
prs_merged_7d7
prs_decided_7d7
prs_merged_30d14
prs_decided_30d14
issue_closed_ratio1
closed_unmerged_prs4
first_time_authors_30d2
first_time_prs_merged_30d2
first_time_prs_decided_30d2
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
15.7/25Owner reach — 150 followers of GamehunterKaan
21.6/25Track record — 20 public repos, account ~6 yr old
Inputs used
followers150
owner_typeUser
is_verified—
owner_loginGamehunterKaan
public_repos20
account_age_days2,291
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 1 days ago
20/20Version history — 24 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesautopwn-suite
ecosystemspypi
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 16 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.mjs, pyproject.toml ([tool.ruff])
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 8 out of 8 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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://kaangultekin.net/projects/autopwn-suite/
10/10Repository description
10/10Topics — 18 topics
0/10Wiki
Inputs used
topicscybersecurity, exploitation, nmap, pentesting, python, python3, scanners, vulnerability-scanners, scanner, scanning, penetration-testing, hacking, hacking-tools, infosec, security, security-tools, cyber-security, cybersecurity-tools
has_wikino
homepagehttps://kaangultekin.net/projects/autopwn-suite/
docs_sitehttps://kaangultekin.net/projects/autopwn-suite/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

97Exceptional · 16% of overall

Security posture

96Exceptional
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 8 out of 8 merged PRs checked by a CI test -- score normalized to 10
2.5/2.5CII-Best-Practices — badge detected: Gold
7.5/7.5Code-Review — all changesets reviewed
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
5/5Fuzzing — project is fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
4/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 8
4.5/5SAST — SAST tool detected but not run on all commits
5/5Security-Policy — security policy file detected
6.8/7.5Signed-Releases — 5 out of the last 5 releases have a total of 8 signed artifacts.
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_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate9.6
Excluded from scoring (no data or not applicable): Branch-Protection. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages24
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:autopwn-suite@2.8.1 runtime dependency closure — what installing the published package pulls in — 24 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.

72Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 95 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.969
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes12,075
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.mjs, pyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 83 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 2 of the last 100 commits are automated dependency updates
8/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 8
Inputs used
has_nixno
has_testsyes
lockfilespoetry.lock
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.83
toolchain_manifests—
dependency_bot_commit_share0.02
How it's scored
0/45Type-checkable code — Python without a type-check config
53.2/55Manageable file sizes — 5/155 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes134,548
source_files_sampled155
oversized_source_files5

Key facts

1,144GitHub stars
8contributors
429commits, last 12 months
1days since last push
41releases
1bus factor
0open 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 ★ / 147 ⇿
0Stars
147Forks
36Releases

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.

0255075100125150144122022-062024-082026-10
Major 1Minor 8Patch 26

Each point covers 4 days.

OpenSSF Scorecard 9.6 / 10
9.6aggregate

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-10-25 01:51 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-Tests8 out of 8 merged PRs checked by a CI test -- score normalized to 10
10CII-Best-Practicesbadge detected: Gold
10Code-Reviewall changesets reviewed
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
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
8Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
9SASTSAST tool detected but not run on all commits
10Security-Policysecurity policy file detected
9Signed-Releases5 out of the last 5 releases have a total of 8 signed artifacts.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
PyPIrequests>=2.33.0pyproject.toml
PyPIrich*pyproject.toml
PyPIbeautifulsoup4*pyproject.toml
PyPIdistro*pyproject.toml
PyPIurllib3^2.8.0pyproject.toml
PyPIcryptography>=50.0.0pyproject.toml
PyPIflask^3.1.3pyproject.toml
PyPIflask-cors^6.0.2pyproject.toml
PyPIwerkzeug^3.1.9pyproject.toml
All dependencies 62

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

RegistryPackageVersionRelation
PyPIbeautifulsoup4—direct
PyPIbeautifulsoup44.13.4direct
PyPIcryptography—direct
PyPIcryptography50.0.2direct
PyPIdistro—direct
PyPIdistro1.9.0direct
PyPIflask—direct
PyPIflask3.1.3direct
PyPIflask-cors—direct
PyPIflask-cors6.0.2direct
PyPIrequests—direct
PyPIrequests2.33.0direct
PyPIrich—direct
PyPIrich14.0.0direct
PyPIrich15.0.0direct
PyPIurllib3—direct
PyPIurllib32.8.0direct
PyPIwerkzeug—direct
PyPIwerkzeug3.1.9direct
PyPIaltgraph0.17.5indirect
PyPIbandit1.9.4indirect
PyPIblinker1.9.0indirect
PyPIbuild1.6.1indirect
PyPIcertifi2026.10.19indirect
PyPIcffi2.1.1indirect
PyPIcharset-normalizer3.4.2indirect
PyPIclick8.3.2indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.6.1indirect
PyPIexceptiongroup1.3.0indirect
PyPIidna3.15indirect
PyPIiniconfig2.1.0indirect
PyPIitsdangerous2.2.0indirect
PyPIjinja23.1.6indirect
PyPImacholib1.16.4indirect
PyPImarkdown-it-py3.0.0indirect
PyPImarkdown-it-py4.2.0indirect
PyPImarkupsafe3.0.3indirect
PyPImdurl0.1.2indirect
PyPIpackaging25.0indirect
PyPIpackaging26.3indirect
PyPIpefile2024.8.26indirect
PyPIpluggy1.5.0indirect
PyPIpoetry-core2.5.0indirect
PyPIpycparser3.11indirect
PyPIpygments2.20.0indirect
PyPIpygments2.21.0indirect
PyPIpyinstaller6.22.3indirect
PyPIpyinstaller-hooks-contrib2026.8indirect
PyPIpyproject-hooks1.3.3indirect
PyPIpytest9.0.3indirect
PyPIpytest-cov4.1.0indirect
PyPIpytest-mock3.14.1indirect
PyPIpywin32-ctypes0.2.3indirect
PyPIpyyaml6.0.3indirect
PyPIruff0.17.1indirect
PyPIsetuptools84.0.0indirect
PyPIsetuptools84.1.0indirect
PyPIsoupsieve2.9indirect
PyPIstevedore5.9.1indirect
PyPItomli2.2.1indirect
PyPItyping-extensions4.13.2indirect
Dependency advisories 0

Installing pypi:autopwn-suite@2.8.1 pulls in 24 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 statistics — PyPI.