Public record
Software health reportschema 0.14.0 · metrics 2.10.0 · 2026-07-18 22:23 UTC

CollaboratingPlatypus / PetaPoco

Official PetaPoco, A tiny ORM-ish thing for your POCO's

C#Custom license★ 2,140 stars⑂ 593 forkssince Mar 2011View on GitHub ↗

CollaboratingPlatypus/PetaPoco holds a health index of 41 out of 100, placing it in the Weak band. It scores highest on Community & Adoption (79/100) and lowest on Vitality (16/100). It was last updated 229 days ago. A single contributor accounts for most of its recent work.

41
overall / 100
Weak

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.

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

Ownership

8 followers1 public reposince Jan 2015

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

Package ecosystems

Metrics by category

Vitality

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

16Critical · 21% of overall
How it's scored
3.6/36Push recencylast push 229 days ago
1.4/36Commit cadence2/52 weeks with commits
5.4/18Commit volume3 commits in the last year
1/10OpenSSF Scorecard: Maintained0 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year3
human_commit_share
days_since_last_push229
active_weeks_last_year2
How it's scored
16.2/27Ships releases5 version tags (no GitHub releases)
0/36Release recencylatest release 2,921 days ago
5.4/27Release cadencea release every ~661.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count5
latest_release_tagv6.0.316
releases_from_tagsyes
days_since_latest_release2,921
mean_days_between_releases661.4
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?

79Good · 17% of overall
How it's scored
54/60Stars2,140 stars
23.1/25Forks593 forks
12.1/15Watchers152 watchers
Inputs used
forks593
stars2,140
watchers152
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
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
66.9/80Total downloads2,753,437 downloads all-time across nuget
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesPetaPoco.Compiled
dependents
ecosystemsnuget
total_downloads2,753,437
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?

62Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
7.9/22.5Commit distributiontop contributor authored 65% of commits
13.5/13.5Contributor breadth37 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled37
top_contributor_share0.65
How it's scored
32.8/42Issue resolution78% of issues closed
21.3/30PR acceptance174/245 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
9/15OpenSSF Scorecard: Code-ReviewFound 6/9 approved changesets -- score normalized to 6
Inputs used
merged_prs174
open_issues106
closed_issues379
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.781
closed_unmerged_prs71
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
6.9/25Owner reach8 followers of CollaboratingPlatypus
14.2/25Track record1 public repos, account ~11 yr old
Inputs used
followers8
owner_typeOrganization
is_verified
owner_loginCollaboratingPlatypus
public_repos1
account_age_days4,198
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on nuget
14/35Publish recencylatest publish 666 days ago
20/20Version history23 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesPetaPoco.Compiled
ecosystemsnuget
any_deprecatedno
min_days_since_publish666

Engineering Quality

Are baseline engineering and documentation practices in place?

28At Risk · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 8 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics2 topics
10/10Wiki
Inputs used
topicsdotnet, orm
has_wikiyes
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?

40Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0/2.5CI-Tests0 out of 8 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-ReviewFound 6/9 approved changesets -- score normalized to 6
2.5/2.5Contributorsproject has 4 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
0.8/7.5Maintained0 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 1
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate4
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

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.

32At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
11/11Static type checkingC# (statically typed)
10/10Reproducible environmentDockerfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeC# (statically typed)
54.6/55Manageable file sizes2/250 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes155,772
source_files_sampled250
oversized_source_files2

Key facts

2,140GitHub stars
37contributors
3commits, last 12 months
229days since last push
5releases
1bus factor
106open issues
NuGetpackage ecosystems

More detail

OpenSSF Scorecard 4.0 / 10
4.0aggregate

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-07-18 22:22 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
0CI-Tests0 out of 8 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 6/9 approved changesets -- score normalized to 6
10Contributorsproject has 4 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
1Maintained0 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 1
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 42
RegistryPackageVersion constraintManifest
NuGetCastle.Core4.2.1PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetMicrosoft.Extensions.Configuration.Binder2.1.0PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetMicrosoft.Extensions.Configuration.CommandLine2.1.0PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetMicrosoft.Extensions.Configuration.Json2.1.0PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetMoq[4.8.2,4.20)PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetNewtonsoft.Json13.0.3PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetShouldly4.0.0PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetSystem.ValueTuple4.5.0PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetxunit2.5.1PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetxunit.abstractions2.0.3PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetxunit.analyzers1.3.0PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetxunit.assert2.5.1PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetxunit.core2.5.1PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetxunit.extensibility.core2.5.1PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetxunit.extensibility.execution2.5.1PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetxunit.runner.visualstudio2.4.1PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetFirebirdSql.Data.FirebirdClient7.5.0PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetMicrosoft.Data.SqlClient2.1.7PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetMicrosoft.SqlServer.Compact4.0.8876.1PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetMySql.Data8.0.21PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetMySqlConnector1.0.1PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetNpgsql4.1.13PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetSystem.Data.SqlClient4.8.6PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetSystem.Data.SQLite.Core1.0.113.1PetaPoco.Tests.Integration/PetaPoco.Tests.Integration.csproj
NuGetCastle.Core4.2.1PetaPoco.Tests.Unit/PetaPoco.Tests.Unit.csproj
NuGetMoq[4.8.2,4.20)PetaPoco.Tests.Unit/PetaPoco.Tests.Unit.csproj
NuGetShouldly3.0.0PetaPoco.Tests.Unit/PetaPoco.Tests.Unit.csproj
NuGetSystem.Configuration.ConfigurationManager4.4.1PetaPoco.Tests.Unit/PetaPoco.Tests.Unit.csproj
NuGetSystem.Threading.Tasks.Extensions4.5.0PetaPoco.Tests.Unit/PetaPoco.Tests.Unit.csproj
NuGetSystem.ValueTuple4.5.0PetaPoco.Tests.Unit/PetaPoco.Tests.Unit.csproj
NuGetxunit2.5.1PetaPoco.Tests.Unit/PetaPoco.Tests.Unit.csproj
NuGetxunit.abstractions2.0.3PetaPoco.Tests.Unit/PetaPoco.Tests.Unit.csproj
NuGetxunit.analyzers1.3.0PetaPoco.Tests.Unit/PetaPoco.Tests.Unit.csproj
NuGetxunit.assert2.5.1PetaPoco.Tests.Unit/PetaPoco.Tests.Unit.csproj
NuGetxunit.core2.5.1PetaPoco.Tests.Unit/PetaPoco.Tests.Unit.csproj
NuGetxunit.extensibility.core2.5.1PetaPoco.Tests.Unit/PetaPoco.Tests.Unit.csproj
NuGetxunit.extensibility.execution2.5.1PetaPoco.Tests.Unit/PetaPoco.Tests.Unit.csproj
NuGetxunit.runner.visualstudio2.4.1PetaPoco.Tests.Unit/PetaPoco.Tests.Unit.csproj
NuGetSystem.Data.SqlClient4.8.6PetaPoco.Tests.Unit/PetaPoco.Tests.Unit.csproj
NuGetMicrosoft.NETFramework.ReferenceAssemblies1.0.2PetaPoco/PetaPoco.csproj
NuGetSystem.Reflection.Emit.ILGeneration4.7.0PetaPoco/PetaPoco.csproj
NuGetSystem.Reflection.Emit.Lightweight4.7.0PetaPoco/PetaPoco.csproj
All dependencies 30

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

RegistryPackageVersionRelation
NuGetCastle.Core4.2.1direct
NuGetFirebirdSql.Data.FirebirdClient7.5.0direct
NuGetMicrosoft.Data.SqlClient2.1.7direct
NuGetMicrosoft.Extensions.Configuration.Binder2.1.0direct
NuGetMicrosoft.Extensions.Configuration.CommandLine2.1.0direct
NuGetMicrosoft.Extensions.Configuration.Json2.1.0direct
NuGetMicrosoft.NETFramework.ReferenceAssemblies1.0.2direct
NuGetMicrosoft.SqlServer.Compact4.0.8876.1direct
NuGetMoqdirect
NuGetMySql.Data8.0.21direct
NuGetMySqlConnector1.0.1direct
NuGetNewtonsoft.Json13.0.3direct
NuGetNpgsql4.1.13direct
NuGetShouldly3.0.0direct
NuGetShouldly4.0.0direct
NuGetSystem.Configuration.ConfigurationManager4.4.1direct
NuGetSystem.Data.SqlClient4.8.6direct
NuGetSystem.Data.SQLite.Core1.0.113.1direct
NuGetSystem.Reflection.Emit.ILGeneration4.7.0direct
NuGetSystem.Reflection.Emit.Lightweight4.7.0direct
NuGetSystem.Threading.Tasks.Extensions4.5.0direct
NuGetSystem.ValueTuple4.5.0direct
NuGetxunit2.5.1direct
NuGetxunit.abstractions2.0.3direct
NuGetxunit.analyzers1.3.0direct
NuGetxunit.assert2.5.1direct
NuGetxunit.core2.5.1direct
NuGetxunit.extensibility.core2.5.1direct
NuGetxunit.extensibility.execution2.5.1direct
NuGetxunit.runner.visualstudio2.4.1direct
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.14.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsNuGet.