Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 19:04 UTC

Tsuk1ko / cq-picsearcher-bot

🤖 基于 saucenao / ascii2d / whatanime 的搜图机器人

JavaScriptGPL-3.0★ 1,603 stars⑂ 217 forkssince Jul 2018View on GitHub ↗
KindNetwork servicehow this is determined

Tsuk1ko/cq-picsearcher-bot holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Vitality (77/100) and lowest on AI Readiness (44/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

67
overall / 100
Good

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.

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

Ownership

神代綺凛Personal account
1,554 followers119 public repossince Jan 2017@arkntools

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
npmcanvaspoints to another repo — not scored3.2.329,137,933161167 days agocanvasgraphicgraphicspixmancairoimageimagespdf

Metrics by category

Vitality

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

77Good · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
7.6/36Commit cadence — 11/52 weeks with commits
16.2/18Commit volume — 63 commits in the last year
10/10OpenSSF Scorecard: Maintained — 29 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year63
human_commit_share1
days_since_last_push2
active_weeks_last_year11
How it's scored
16.2/27Ships releases — 100 version tags (no GitHub releases)
36/36Release recency — latest release 2 days ago
27/27Release cadence — a release every ~38.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv3.26.1
releases_from_tagsyes
days_since_latest_release2
mean_days_between_releases38.1
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?

65Good · 17% of overall
How it's scored
52/60Stars — 1,603 stars
19.5/25Forks — 217 forks
7.4/15Watchers — 22 watchers
Inputs used
forks217
stars1,603
watchers22
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno

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 factor — 1 contributor(s) cover half of all commits
0.2/22.5Commit distribution — top contributor authored 99% of commits
9.5/13.5Contributor breadth — 7 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.992
How it's scored
42/42Issue resolution — 100% of issues closed
24.3/30PR acceptance — 38/47 decided PRs merged
6.5/13Newcomer PR acceptance — 1/2 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/30 approved changesets -- score normalized to 0
Inputs used
merged_prs38
open_issues0
closed_issues288
prs_merged_7d2
prs_decided_7d3
prs_merged_30d2
prs_decided_30d3
issue_closed_ratio1
closed_unmerged_prs9
first_time_authors_30d2
first_time_prs_merged_30d1
first_time_prs_decided_30d2
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
22.9/25Owner reach — 1,554 followers of Tsuk1ko
25/25Track record — 119 public repos, account ~9 yr old
Inputs used
followers1,554
owner_typeUser
is_verified—
owner_loginTsuk1ko
public_repos119
account_age_days3,542
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

54Moderate · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
0/24Tests present
16/16Linter config — eslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 2 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://moe.best/projects/qq-robot-picfinder.html
10/10Repository description
10/10Topics — 6 topics
10/10Wiki
Inputs used
topicsqq, robot, pixiv, anime, go-cqhttp, qq-bot
has_wikiyes
homepagehttps://moe.best/projects/qq-robot-picfinder.html
docs_sitehttps://moe.best/projects/qq-robot-picfinder.html
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

60Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 0 out of 2 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 1/30 approved changesets -- score normalized to 0
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
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 29 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
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_aggregate4.9
Excluded from scoring (no data or not applicable): Signed-Releases. 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_packages36
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 npm:canvas@3.2.3 runtime dependency closure — what installing the published package pulls in — 36 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 instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 78 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.78
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format config — eslint.config.mjs
11/11Static type checking — jsconfig.json
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsjsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — JavaScript with type-check config (jsconfig.json)
55/55Manageable file sizes — 0/94 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes30,413
source_files_sampled94
oversized_source_files0

Key facts

1,603GitHub stars
7contributors
63commits, last 12 months
2days since last push
100releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • npm package 'canvas' points at a different repository (https://github.com/Automattic/node-canvas); excluded from ecosystem scoring

More detail

Star and fork history 0 ★ / 217 ⇿
0Stars
217Forks
98Releases

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.

0408012016020024021552018-072022-082026-09
Major 1Minor 34Patch 63

Each point covers 8 days.

OpenSSF Scorecard 4.9 / 10
4.9aggregate

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-09-14 19:04 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 2 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/30 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained29 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 50
RegistryPackageVersion constraintManifest
npm@jimp/core^1.6.1package.json
npm@jimp/js-bmp^1.6.1package.json
npm@jimp/js-gif^1.6.1package.json
npm@jimp/js-jpeg^1.6.1package.json
npm@jimp/js-png^1.6.1package.json
npm@jimp/js-tiff^1.6.1package.json
npm@jimp/plugin-blit^1.6.1package.json
npm@jimp/plugin-resize^1.6.1package.json
npm@jimp/plugin-rotate^1.6.1package.json
npm@json2csv/plainjs^7.0.6package.json
npm@koa/router^15.6.0package.json
npm@msgpack/msgpack^3.1.3package.json
npm@napi-rs/canvas^1.0.1package.json
npm@tsuk1ko/cq-websocket^3.0.0package.json
npmawait-lock^2.2.2package.json
npmaxios^1.18.1package.json
npmcheerio^1.2.0package.json
npmcomment-json^4.6.2package.json
npmcompare-versions^6.1.1package.json
npmcron-parser^5.6.1package.json
npmdayjs^1.11.21package.json
npmdeep-freeze^0.0.1package.json
npmdotenv^17.4.2package.json
npmes-toolkit^1.49.0package.json
npmescape-string-regexp^5.0.0package.json
npmflaresolverr-client^1.2.0package.json
npmform-data^4.0.6package.json
npmfs-extra^11.3.5package.json
npmhttp-terminator^3.2.0package.json
npmhttps-proxy-agent^5.0.1package.json
npmimage-size^2.0.2package.json
npmjsonc^2.0.0package.json
npmklaw-sync^7.0.0package.json
npmkoa^3.2.1package.json
npmmd5^2.3.0package.json
npmminimist^1.2.8package.json
npmnamed-regexp-groups^1.0.6package.json
npmnode-cache^5.1.2package.json
npmpm2^7.0.1package.json
npmpromise-limit^2.7.0package.json
npmqs^6.15.3package.json
npmrandom-seed^0.3.0package.json
npmremove-markdown^0.6.4package.json
npmsocks-proxy-agent^7.0.0package.json
npmtencentcloud-sdk-nodejs-ocr^4.1.257package.json
npmtough-cookie^6.0.1package.json
npmurl-join^5.0.0package.json
npmwebp-wasm^1.0.6package.json
npmzod^3.25.76package.json
npmcanvas^2.11.2libs/canvas/package.json
All dependencies 60

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

RegistryPackageVersionRelation
npm@jimp/core^1.6.1direct
npm@jimp/js-bmp^1.6.1direct
npm@jimp/js-gif^1.6.1direct
npm@jimp/js-jpeg^1.6.1direct
npm@jimp/js-png^1.6.1direct
npm@jimp/js-tiff^1.6.1direct
npm@jimp/plugin-blit^1.6.1direct
npm@jimp/plugin-resize^1.6.1direct
npm@jimp/plugin-rotate^1.6.1direct
npm@json2csv/plainjs^7.0.6direct
npm@koa/router^15.6.0direct
npm@msgpack/msgpack^3.1.3direct
npm@napi-rs/canvas^1.0.1direct
npm@tsuk1ko/cq-websocket^3.0.0direct
npmawait-lock^2.2.2direct
npmaxios^1.18.1direct
npmcanvas^2.11.2direct
npmcheerio^1.2.0direct
npmcomment-json^4.6.2direct
npmcompare-versions^6.1.1direct
npmcron-parser^5.6.1direct
npmdayjs^1.11.21direct
npmdeep-freeze^0.0.1direct
npmdotenv^17.4.2direct
npmes-toolkit^1.49.0direct
npmescape-string-regexp^5.0.0direct
npmflaresolverr-client^1.2.0direct
npmform-data^4.0.6direct
npmfs-extra^11.3.5direct
npmhttp-terminator^3.2.0direct
npmhttps-proxy-agent^5.0.1direct
npmimage-size^2.0.2direct
npmjsonc^2.0.0direct
npmklaw-sync^7.0.0direct
npmkoa^3.2.1direct
npmmd5^2.3.0direct
npmminimist^1.2.8direct
npmnamed-regexp-groups^1.0.6direct
npmnode-cache^5.1.2direct
npmpm2^7.0.1direct
npmpromise-limit^2.7.0direct
npmqs^6.15.3direct
npmrandom-seed^0.3.0direct
npmremove-markdown^0.6.4direct
npmsocks-proxy-agent^7.0.0direct
npmtencentcloud-sdk-nodejs-ocr^4.1.257direct
npmtough-cookie^6.0.1direct
npmurl-join^5.0.0direct
npmwebp-wasm^1.0.6direct
npmzod^3.25.76direct
npm@antfu/eslint-config^9.1.0indirect
npm@tsuk1ko/eslint-config^2.1.1indirect
npm@tsuk1ko/postversion^1.0.2indirect
npm@types/fs-extra^11.0.4indirect
npm@types/node^24.13.2indirect
npmeslint^10.6.0indirect
npmeslint-config-prettier^10.1.8indirect
npmnodemon^3.1.14indirect
npmprettier^3.9.1indirect
npmtypeof-jsonc^1.1.10indirect
Dependency advisories 0

Installing npm:canvas@3.2.3 pulls in 36 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 — npm.