Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-29 12:53 UTC

ImoutoChan / ImoutoBooruParser

Library designed to parse data from booru-like websites such as danbooru.donmai.us, yande.re, gelbooru.com, and chan.sankakucomplex.com.

C#MIT★ 15 stars⑂ 2 forkssince Sep 2017View on GitHub ↗

ImoutoChan/ImoutoBooruParser holds a health index of 54 out of 100, placing it in the Moderate band. It scores highest on Vitality (66/100) and lowest on AI Readiness (37/100). It was last updated today. A single contributor accounts for most of its recent work.

54
overall / 100
Moderate

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.

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

Ownership

ImoutoChanPersonal account
31 followers44 public repossince Oct 2015

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
NuGetImouto.BooruParser4.4.0-510 days agoboorusearchparserdanboorusankakuchannelyande.reyanderegelbooruimageboardimageartanimeartanime

Metrics by category

Vitality

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

66Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
3.5/36Commit cadence5/52 weeks with commits
11.3/18Commit volume17 commits in the last year
5/10OpenSSF Scorecard: Maintained7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year17
human_commit_share0.99
days_since_last_push0
active_weeks_last_year5
How it's scored
16.2/27Ships releases55 version tags (no GitHub releases)
36/36Release recencylatest release 0 days ago
19.8/27Release cadencea release every ~47.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count55
latest_release_tagv4.4.0
releases_from_tagsyes
days_since_latest_release0
mean_days_between_releases47.9
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?

40Weak · 17% of overall
How it's scored
18.6/60Stars15 stars
0/25Forks2 forks
0/15Watchers1 watchers
Inputs used
forks2
stars15
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
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
How it's scored
47.1/80Total downloads33,771 downloads all-time across nuget
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesImouto.BooruParser
dependents
ecosystemsnuget
total_downloads33,771
monthly_downloads
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?

55Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.1/22.5Commit distributiontop contributor authored 100% of commits
2.7/13.5Contributor breadth2 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.995
How it's scored
42/42Issue resolution100% of issues closed
20/30PR acceptance2/3 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_prs2
open_issues0
closed_issues4
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs1
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
10.8/25Owner reach31 followers of ImoutoChan
24/25Track record44 public repos, account ~10 yr old
Inputs used
followers31
owner_typeUser
is_verified
owner_loginImoutoChan
public_repos44
account_age_days3,981
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 nuget
35/35Publish recencylatest publish 0 days ago
20/20Version history51 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesImouto.BooruParser
ecosystemsnuget
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

38Weak · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics15 topics
0/10Wiki
Inputs used
topicsimage, tags, tag, anime, parser, booru, danbooru, sankakucomplex, sankakuchannel, yandere, csharp, library, netstandard, gelbooru, dotnet
has_wikino
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

66Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Testsno data
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
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
3.8/7.5Maintained7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
5/5Packagingpackaging workflow detected
3.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
6.8/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.7
Excluded from scoring (no data or not applicable): CI-Tests, Signed-Releases. Remaining weights renormalized.

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_packages13
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 13 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.

37Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
2.2/40Legible commit history4 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.04
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapImouto.BooruParser.Example/Imouto.BooruParser.Example.csproj, Imouto.BooruParser.Tests/Imouto.BooruParser.Tests.csproj, Imouto.BooruParser/Imouto.BooruParser.csproj (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checkingC# (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance1 of the last 100 commits are automated dependency updates
7/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsImouto.BooruParser.Example/Imouto.BooruParser.Example.csproj, Imouto.BooruParser.Tests/Imouto.BooruParser.Tests.csproj, Imouto.BooruParser/Imouto.BooruParser.csproj
dependency_bot_commit_share0.01
How it's scored
45/45Type-checkable codeC# (statically typed)
55/55Manageable file sizes0/42 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes18,845
source_files_sampled42
oversized_source_files0

Key facts

15GitHub stars
2contributors
17commits, last 12 months
0days since last push
55releases
1bus factor
0open issues
NuGetpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 2 ⇿
0Stars
2Forks
1Releases

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.

111222212025-012025-022025-03
Major 0Minor 1Patch 0
OpenSSF Scorecard 5.7 / 10
5.7aggregate

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-29 12:53 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
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
0Fuzzingproject is not fuzzed
10Licenselicense file detected
5Maintained7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
10Packagingpackaging workflow detected
7Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 15
RegistryPackageVersion constraintManifest
NuGetMicrosoft.Extensions.DependencyInjection.Abstractions10.0.9Imouto.BooruParser.Example/Imouto.BooruParser.Example.csproj
NuGetAwesomeAssertions9.4.0Imouto.BooruParser.Tests/Imouto.BooruParser.Tests.csproj
NuGetMicrosoft.Extensions.Caching.Memory10.0.9Imouto.BooruParser.Tests/Imouto.BooruParser.Tests.csproj
NuGetMicrosoft.Extensions.DependencyInjection10.0.9Imouto.BooruParser.Tests/Imouto.BooruParser.Tests.csproj
NuGetMicrosoft.NET.Test.Sdk18.7.0Imouto.BooruParser.Tests/Imouto.BooruParser.Tests.csproj
NuGetMoq4.20.72Imouto.BooruParser.Tests/Imouto.BooruParser.Tests.csproj
NuGetVerify.Xunit31.12.5Imouto.BooruParser.Tests/Imouto.BooruParser.Tests.csproj
NuGetxunit2.9.3Imouto.BooruParser.Tests/Imouto.BooruParser.Tests.csproj
NuGetxunit.runner.visualstudio3.1.5Imouto.BooruParser.Tests/Imouto.BooruParser.Tests.csproj
NuGetFlurl.Http4.0.2Imouto.BooruParser/Imouto.BooruParser.csproj
NuGetHtmlAgilityPack1.12.4Imouto.BooruParser/Imouto.BooruParser.csproj
NuGetMicrosoft.Extensions.Caching.Memory10.0.9Imouto.BooruParser/Imouto.BooruParser.csproj
NuGetMicrosoft.Extensions.DependencyInjection.Abstractions10.0.9Imouto.BooruParser/Imouto.BooruParser.csproj
NuGetMicrosoft.Extensions.Options.ConfigurationExtensions10.0.9Imouto.BooruParser/Imouto.BooruParser.csproj
NuGetSystem.IdentityModel.Tokens.Jwt8.19.1Imouto.BooruParser/Imouto.BooruParser.csproj
All dependencies 13

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

RegistryPackageVersionRelation
NuGetAwesomeAssertions9.4.0direct
NuGetFlurl.Http4.0.2direct
NuGetHtmlAgilityPack1.12.4direct
NuGetMicrosoft.Extensions.Caching.Memory10.0.9direct
NuGetMicrosoft.Extensions.DependencyInjection10.0.9direct
NuGetMicrosoft.Extensions.DependencyInjection.Abstractions10.0.9direct
NuGetMicrosoft.Extensions.Options.ConfigurationExtensions10.0.9direct
NuGetMicrosoft.NET.Test.Sdk18.7.0direct
NuGetMoq4.20.72direct
NuGetSystem.IdentityModel.Tokens.Jwt8.19.1direct
NuGetVerify.Xunit31.12.5direct
NuGetxunit2.9.3direct
NuGetxunit.runner.visualstudio3.1.5direct
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 13 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 statisticsNuGet.