Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-17 01:14 UTC

cycodehq / cycode-cli

Boost security in your dev lifecycle via SAST, SCA, Secrets & IaC scanning

PythonMIT★ 99 stars⑂ 70 forkssince Jul 2022View on GitHub ↗
KindCommand-line toolMCP serverLibraryhow this is determined

cycodehq/cycode-cli holds a health index of 92 out of 100, placing it in the Excellent band. It scores highest on Vitality (95/100) and lowest on AI Readiness (57/100). It was last updated today. 2 contributors account for most of its recent work.

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

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

Ownership

CycodeOrganization · verified domain
21 followers8 public repossince Jul 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIcycode3.27.175,4605138 days agosecret-scancycodedevopstokensecretsecuritycode

Metrics by category

Vitality

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

95Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
33.9/36Commit cadence — 49/52 weeks with commits
18/18Commit volume — 190 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_year190
human_commit_share0.64
days_since_last_push0
active_weeks_last_year49
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 8 days ago
27/27Release cadence — a release every ~7.4 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv3.27.1
releases_from_tagsno
days_since_latest_release8
mean_days_between_releases7.4

Community & Adoption

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

66Good · 17% of overall
How it's scored
32.3/60Stars — 99 stars
15.3/25Forks — 70 forks
6.5/15Watchers — 16 watchers
Inputs used
forks70
stars99
watchers16
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
65/80Monthly downloads — 75,460 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagescycode
dependents—
ecosystemspypi
total_downloads—
monthly_downloads75,460
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?

79Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
13.7/22.5Commit distribution — top contributor authored 39% of commits
13.5/13.5Contributor breadth — 39 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled39
top_contributor_share0.389
How it's scored
0/42Issue resolution — no issues or no data
26.6/30PR acceptance — 521/587 decided PRs merged
6.5/13Newcomer PR acceptance — 1/2 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs521
open_issues0
closed_issues0
prs_merged_7d1
prs_decided_7d1
prs_merged_30d6
prs_decided_30d7
issue_closed_ratio—
closed_unmerged_prs66
first_time_authors_30d2
first_time_prs_merged_30d1
first_time_prs_decided_30d2
Excluded from scoring (no data or not applicable): Issue resolution. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
9.7/25Owner reach — 21 followers of cycodehq
18.9/25Track record — 8 public repos, account ~7 yr old
Inputs used
followers21
owner_typeOrganization
is_verifiedyes
owner_logincycodehq
public_repos8
account_age_days2,695

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows — 7 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 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
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://www.cycode.com
10/10Repository description
10/10Topics — 7 topics
0/10Wiki
Inputs used
topicscode, sast, sca, secrets, secure, security, cycode
has_wikino
homepagehttps://www.cycode.com
docs_sitehttps://www.cycode.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

77Good · 16% of overall
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 — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 5 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
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 — 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
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.1
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_packages52
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:cycode@3.27.1 runtime dependency closure — what installing the published package pulls in — 52 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.

57Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://www.cycode.com/llms.txt)
40/40Legible commit history — 53 of 64 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://www.cycode.com/llms.txt
legible_history_share0.828
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 47 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 36 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.47
toolchain_manifests—
dependency_bot_commit_share0.36
How it's scored
0/45Type-checkable code — Python without a type-check config
54.7/55Manageable file sizes — 2/367 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes67,402
source_files_sampled367
oversized_source_files2
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs—
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

99GitHub stars
39contributors
190commits, last 12 months
0days since last push
100releases
2bus 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 ★ / 70 ⇿
0Stars
70Forks
100Releases

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.

013253850637569172022-112024-112026-11
Major 2Minor 35Patch 63

Each point covers 4 days.

OpenSSF Scorecard 7.1 / 10
7.1aggregate

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-17 01:14 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-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not 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
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 21
RegistryPackageVersion constraintManifest
PyPIclick>=8.1.0,<8.2.0pyproject.toml
PyPIcolorama>=0.4.3,<0.5.0pyproject.toml
PyPIpyyaml>=6.0,<7.0pyproject.toml
PyPImarshmallow>=4.1.2,<5.0.0pyproject.toml
PyPIgitpython>=3.2.1,<3.3.0pyproject.toml
PyPIarrow>=1.0.0,<1.5.0pyproject.toml
PyPIrequests>=2.33.0,<3.0pyproject.toml
PyPIurllib3>=2.8.0,<3.0.0pyproject.toml
PyPIpyjwt>=2.15.0,<3.0pyproject.toml
PyPIrich>=15.0.0,<16.0.0pyproject.toml
PyPIpatch-ng1.19.1pyproject.toml
PyPItyper^0.15.3pyproject.toml
PyPItenacity>=9.2.1,<9.3.0pyproject.toml
PyPImcp>=1.30.0,<2.0.0pyproject.toml
PyPItruststore>=0.10.4,<0.11.0pyproject.toml
PyPIpywin32>=312,<313pyproject.toml
PyPIpydantic>=2.11.5,<3.0.0pyproject.toml
PyPIpathvalidate>=3.3.1,<4.0.0pyproject.toml
PyPItomli-w>=1.0.0,<2.0.0pyproject.toml
PyPItomli>=2.0.0,<3.0.0pyproject.toml
PyPIanyio>=4.14.2,<5.0.0pyproject.toml
All dependencies 75

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

RegistryPackageVersionRelation
PyPIanyio4.15.1direct
PyPIarrow1.4.0direct
PyPIclick8.1.8direct
PyPIcolorama0.4.6direct
PyPIgitpython3.2.1direct
PyPImarshmallow4.3.1direct
PyPImcp1.30.0direct
PyPIpatch-ng1.19.1direct
PyPIpathvalidate3.3.1direct
PyPIpydantic2.13.4direct
PyPIpyjwt2.15.1direct
PyPIpywin32312direct
PyPIpyyaml6.0.3direct
PyPIrequests2.34.2direct
PyPIrich15.0.0direct
PyPItenacity9.2.1direct
PyPItomli2.4.1direct
PyPItomli-w1.2.0direct
PyPItruststore0.10.4direct
PyPItyper0.15.4direct
PyPIurllib32.8.0direct
PyPIaltgraph0.17.5indirect
PyPIannotated-types0.8.0indirect
PyPIattrs26.1.0indirect
PyPIbackports-datetime-fromisoformat2.0.3indirect
PyPIcertifi2026.10.18indirect
PyPIcffi2.1.0indirect
PyPIcharset-normalizer3.4.9indirect
PyPIcoverage7.10.7indirect
PyPIcryptography50.0.1indirect
PyPIdunamai1.26.3indirect
PyPIexceptiongroup1.3.1indirect
PyPIgitdb4.0.12indirect
PyPIh110.16.0indirect
PyPIhttpcore1.0.9indirect
PyPIhttpx0.28.1indirect
PyPIhttpx-sse0.4.3indirect
PyPIidna3.18indirect
PyPIiniconfig2.3.0indirect
PyPIjsonschema4.26.0indirect
PyPIjsonschema-specifications2025.9.1indirect
PyPImacholib1.16.4indirect
PyPImarkdown-it-py4.2.0indirect
PyPImdurl0.1.2indirect
PyPImock5.2.0indirect
PyPIpackaging26.2indirect
PyPIpefile2024.8.26indirect
PyPIpluggy1.6.0indirect
PyPIpycparser3.0indirect
PyPIpydantic-core2.46.4indirect
PyPIpydantic-settings2.14.2indirect
PyPIpyfakefs6.2.0indirect
PyPIpygments2.20.0indirect
PyPIpyinstaller6.22.2indirect
PyPIpyinstaller-hooks-contrib2026.6indirect
PyPIpytest9.0.3indirect
PyPIpytest-mock3.15.1indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpython-dotenv1.2.2indirect
PyPIpython-multipart0.0.32indirect
PyPIpywin32-ctypes0.2.3indirect
PyPIreferencing0.37.0indirect
PyPIresponses0.26.3indirect
PyPIrpds-py0.30.0indirect
PyPIruff0.16.9indirect
PyPIsetuptools84.1.0indirect
PyPIshellingham1.5.4indirect
PyPIsix1.17.0indirect
PyPIsmmap5.0.3indirect
PyPIsse-starlette3.4.6indirect
PyPIstarlette1.3.1indirect
PyPItyping-extensions4.16.0indirect
PyPItyping-inspection0.4.2indirect
PyPItzdata2026.3indirect
PyPIuvicorn0.51.0indirect
Dependency advisories 0

Installing pypi:cycode@3.27.1 pulls in 52 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.