Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 13:53 UTC

AngeloDotNet / MinimalApi.Identity

A set of libraries to easily integrate and extend authentication in ASP.NET Core projects, using ASP.NET Core Identity.

C#MIT★ 6 stars⑂ 0 forkssince Jun 2025View on GitHub ↗

AngeloDotNet/MinimalApi.Identity holds a health index of 51 out of 100, placing it in the Moderate band. It scores highest on Vitality (60/100) and lowest on Community & Adoption (29/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Angelo PirolaPersonal account
27 followers127 public repossince Apr 2019

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Metrics by category

Vitality

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

60Moderate · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
34.6/36Commit cadence50/52 weeks with commits
18/18Commit volume2,750 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year2,750
human_commit_share
days_since_last_push0
active_weeks_last_year50
How it's scored
0/27Ships releasesno releases published
0/36Release recencyno releases
0/27Release cadenceno releases
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count0
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?

29At Risk · 17% of overall
How it's scored
11.3/60Stars6 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars6
watchers0
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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

52Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.4/22.5Commit distributiontop contributor authored 98% of commits
4.1/13.5Contributor breadth3 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.984
How it's scored
42/42Issue resolution100% of issues closed
29.7/30PR acceptance323/326 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_prs323
open_issues0
closed_issues1
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs3
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
10.4/25Owner reach27 followers of AngeloDotNet
25/25Track record127 public repos, account ~7 yr old
Inputs used
followers27
owner_typeUser
is_verified
owner_loginAngeloDotNet
public_repos127
account_age_days2,649
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

53Moderate · 19% of overall
How it's scored
24/24CI workflows16 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsno
has_editorconfigyes
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics7 topics
0/10Wiki
Inputs used
topicsaspnetcore, minimal-api, c-sharp, hacktoberfest, hacktoberfest-accepted, nuget-package, aspnetcoreidentity
has_wikino
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

57Moderate · 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-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
2.5/2.5Contributorsproject has 6 contributing companies or organizations
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
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.7
Excluded from scoring (no data or not applicable): Branch-Protection, CI-Tests, Signed-Releases. 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.

50Moderate · 4% of overall
How it's scored
45/45Agent instructions.github/copilot-instructions.md
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.github/copilot-instructions.md
agent_instruction_max_bytes4,819
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)
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileno
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. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeC# (statically typed)
55/55Manageable file sizes0/226 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes33,336
source_files_sampled226
oversized_source_files0

Key facts

6GitHub stars
3contributors
2,750commits, last 12 months
0days since last push
0releases
1bus factor
0open issues
NuGetpackage ecosystems

More detail

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-07-17 13:53 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
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
10Contributorsproject has 6 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
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
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 2
RegistryPackageVersion constraintManifest
NuGetIdentity.Module.API2.5.479IdentityManager.API/IdentityManager.API.csproj
NuGetMicrosoft.EntityFrameworkCore.Tools9.0.17IdentityManager.API/IdentityManager.API.csproj
All dependencies 46

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

RegistryPackageVersionRelation
NuGetIdentity.Module.API2.5.479direct
NuGetMicrosoft.EntityFrameworkCore.Tools9.0.17direct
NuGetMicrosoft.EntityFrameworkCore.Tools9.0.2direct
NuGetAWSSDK.S34.0.101.2indirect
NuGetEntityFrameworkCore.Exceptions.MySQL8.1.3indirect
NuGetEntityFrameworkCore.Exceptions.MySQL.Pomelo8.1.3indirect
NuGetEntityFrameworkCore.Exceptions.PostgreSQL8.1.3indirect
NuGetEntityFrameworkCore.Exceptions.Sqlite8.1.3indirect
NuGetEntityFrameworkCore.Exceptions.SqlServer8.1.3indirect
NuGetFluentValidation.DependencyInjectionExtensions12.1.1indirect
NuGetIdentity.Module.AccountManager2.5.142indirect
NuGetIdentity.Module.AuthManager2.5.107indirect
NuGetIdentity.Module.ClaimsManager2.5.50indirect
NuGetIdentity.Module.Core2.5.240indirect
NuGetIdentity.Module.EmailManager2.5.110indirect
NuGetIdentity.Module.LicenseManager2.5.114indirect
NuGetIdentity.Module.ModuleManager2.5.51indirect
NuGetIdentity.Module.PolicyManager2.5.130indirect
NuGetIdentity.Module.ProfileManager2.5.120indirect
NuGetIdentity.Module.RolesManager2.5.78indirect
NuGetIdentity.Module.Shared2.5.135indirect
NuGetMailKit4.10.0indirect
NuGetMailKit4.17.0indirect
NuGetMicrosoft.AspNetCore.Authentication.JwtBearer8.0.13indirect
NuGetMicrosoft.AspNetCore.Authentication.JwtBearer9.0.17indirect
NuGetMicrosoft.AspNetCore.Diagnostics.EntityFrameworkCore9.0.17indirect
NuGetMicrosoft.AspNetCore.Identity.EntityFrameworkCore8.0.13indirect
NuGetMicrosoft.AspNetCore.Identity.EntityFrameworkCore9.0.17indirect
NuGetMicrosoft.AspNetCore.OpenApi8.0.13indirect
NuGetMicrosoft.EntityFrameworkCore9.0.17indirect
NuGetMicrosoft.EntityFrameworkCore9.0.2indirect
NuGetMicrosoft.EntityFrameworkCore.Sqlite9.0.17indirect
NuGetMicrosoft.EntityFrameworkCore.SqlServer9.0.17indirect
NuGetMicrosoft.EntityFrameworkCore.SqlServer9.0.2indirect
NuGetNpgsql.EntityFrameworkCore.PostgreSQL9.0.4indirect
NuGetPomelo.EntityFrameworkCore.MySql9.0.0indirect
NuGetScrutor7.0.0indirect
NuGetSerilog4.4.0indirect
NuGetSerilog.AspNetCore10.0.0indirect
NuGetSerilog.Enrichers.Environment3.0.1indirect
NuGetSerilog.Enrichers.Thread4.0.0indirect
NuGetSerilog.Sinks.Console6.1.1indirect
NuGetSerilog.Sinks.File7.0.0indirect
NuGetSwashbuckle.AspNetCore7.2.0indirect
NuGetSwashbuckle.AspNetCore7.3.2indirect
NuGetSwashbuckle.AspNetCore.SwaggerGen7.3.2indirect
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.11.0 — full methodology · metrics wiki.

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