Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 11:55 UTC

okta / okta-sdk-dotnet

A .NET SDK for interacting with the Okta management API, enabling server-side code to manage Okta users, groups, applications, and more.

C#Custom license★ 182 stars⑂ 105 forkssince Nov 2014View on GitHub ↗

okta/okta-sdk-dotnet holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (90/100) and lowest on Engineering Quality (42/100). It was last updated 30 days ago. 3 contributors account for most of its recent work.

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

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

Ownership

Okta, IncOrganization · verified domain
684 followers90 public repossince Aug 2010

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
NuGetOkta.Sdk10.1.0-7348 days agooktaapiauthenticationidentitymanagement

Metrics by category

Vitality

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

81Excellent · 21% of overall
How it's scored
28.8/36Push recency — last push 30 days ago
17.3/36Commit cadence — 25/52 weeks with commits
17.9/18Commit volume — 97 commits in the last year
10/10OpenSSF Scorecard: Maintained — 18 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year97
human_commit_share1
days_since_last_push30
active_weeks_last_year25
How it's scored
27/27Ships releases — 85 releases published
36/36Release recency — latest release 48 days ago
19.8/27Release cadence — a release every ~59.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count85
latest_release_tagv10.1.0
releases_from_tagsno
days_since_latest_release48
mean_days_between_releases59.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?

80Excellent · 17% of overall
How it's scored
36.6/60Stars — 182 stars
16.8/25Forks — 105 forks
13.1/15Watchers — 226 watchers
Inputs used
forks105
stars182
watchers226
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

86Excellent
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
74.2/80Total downloads — 13,773,003 downloads all-time across nuget
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesOkta.Sdk
dependents—
ecosystemsnuget
total_downloads13,773,003
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?

90Excellent · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
16.5/22.5Commit distribution — top contributor authored 27% of commits
13.5/13.5Contributor breadth — 27 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled27
top_contributor_share0.267
How it's scored
41.7/42Issue resolution — 99% of issues closed
23/30PR acceptance — 391/511 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs391
open_issues3
closed_issues381
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.992
closed_unmerged_prs120
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
30/30Ownership backing — organization-owned
20/20Verified domain
20.4/25Owner reach — 684 followers of okta
25/25Track record — 90 public repos, account ~16 yr old
Inputs used
followers684
owner_typeOrganization
is_verifiedyes
owner_loginokta
public_repos90
account_age_days5,913

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on nuget
35/35Publish recency — latest publish 48 days ago
20/20Version history — 73 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesOkta.Sdk
ecosystemsnuget
any_deprecatedno
min_days_since_publish48

Engineering Quality

Are baseline engineering and documentation practices in place?

42Weak · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 14 out of 14 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
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?

73Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 14 out of 14 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 4 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 18 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
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 — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate6.6
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages26
unassessed_packages1
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 26 resolved dependencies against OSV. 1 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

60Moderate · 4% of overall
How it's scored
45/45Agent instructions — docs/Agent.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 87 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.87
agent_instruction_filesdocs/Agent.md
agent_instruction_max_bytes1,228
How it's scored
12.6/18One-command bootstrap — src/Okta.Sdk.Extensions/Okta.Sdk.Extensions.csproj, src/Okta.Sdk.IntegrationTest/Okta.Sdk.IntegrationTest.csproj, src/Okta.Sdk.UnitTest/Okta.Sdk.UnitTest.csproj (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checking — C# (statically typed)
0/10Reproducible environment
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 — no data
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestssrc/Okta.Sdk.Extensions/Okta.Sdk.Extensions.csproj, src/Okta.Sdk.IntegrationTest/Okta.Sdk.IntegrationTest.csproj, src/Okta.Sdk.UnitTest/Okta.Sdk.UnitTest.csproj, src/Okta.Sdk/Okta.Sdk.csproj
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable code — C# (statically typed)
53.9/55Manageable file sizes — 41/2,094 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes168,442
source_files_sampled2,094
oversized_source_files41

Key facts

182GitHub stars
27contributors
97commits, last 12 months
30days since last push
85releases
3bus factor
3open issues
—package ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 105 ⇿
0Stars
105Forks
83Releases

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.

02040608010012010532015-012020-102026-07
Major 10Minor 14Patch 46

Each point covers 11 days.

OpenSSF Scorecard 6.6 / 10
6.6aggregate

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-10-21 11:54 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests14 out of 14 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 4 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained18 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 38
RegistryPackageVersion constraintManifest
NuGetMicrosoft.CSharp4.7.0src/Okta.Sdk.Extensions/Okta.Sdk.Extensions.csproj
NuGetRestSharp112.1.0src/Okta.Sdk.Extensions/Okta.Sdk.Extensions.csproj
NuGetxunit.abstractions2.0.3src/Okta.Sdk.Extensions/Okta.Sdk.Extensions.csproj
NuGetSystem.Text.Json9.0.0src/Okta.Sdk.Extensions/Okta.Sdk.Extensions.csproj
NuGetFluentAssertions8.8.0src/Okta.Sdk.IntegrationTest/Okta.Sdk.IntegrationTest.csproj
NuGetMicrosoft.Bcl.AsyncInterfaces9.0.0src/Okta.Sdk.IntegrationTest/Okta.Sdk.IntegrationTest.csproj
NuGetMicrosoft.NET.Test.Sdk18.0.1src/Okta.Sdk.IntegrationTest/Okta.Sdk.IntegrationTest.csproj
NuGetNSubstitute5.3.0src/Okta.Sdk.IntegrationTest/Okta.Sdk.IntegrationTest.csproj
NuGetPolly8.6.5src/Okta.Sdk.IntegrationTest/Okta.Sdk.IntegrationTest.csproj
NuGetRestSharp112.1.0src/Okta.Sdk.IntegrationTest/Okta.Sdk.IntegrationTest.csproj
NuGetxunit2.9.3src/Okta.Sdk.IntegrationTest/Okta.Sdk.IntegrationTest.csproj
NuGetxunit.runner.visualstudio3.1.5src/Okta.Sdk.IntegrationTest/Okta.Sdk.IntegrationTest.csproj
NuGetcoverlet.collector6.0.4src/Okta.Sdk.IntegrationTest/Okta.Sdk.IntegrationTest.csproj
NuGetcoverlet.msbuild6.0.4src/Okta.Sdk.IntegrationTest/Okta.Sdk.IntegrationTest.csproj
NuGetSystem.Linq.Async*src/Okta.Sdk.IntegrationTest/Okta.Sdk.IntegrationTest.csproj
NuGetcoverlet.collector6.0.4src/Okta.Sdk.UnitTest/Okta.Sdk.UnitTest.csproj
NuGetcoverlet.msbuild6.0.4src/Okta.Sdk.UnitTest/Okta.Sdk.UnitTest.csproj
NuGetFluentAssertions8.8.0src/Okta.Sdk.UnitTest/Okta.Sdk.UnitTest.csproj
NuGetMicrosoft.Bcl.AsyncInterfaces9.0.0src/Okta.Sdk.UnitTest/Okta.Sdk.UnitTest.csproj
NuGetMicrosoft.NET.Test.Sdk18.0.1src/Okta.Sdk.UnitTest/Okta.Sdk.UnitTest.csproj
NuGetMoq4.20.72src/Okta.Sdk.UnitTest/Okta.Sdk.UnitTest.csproj
NuGetNSubstitute5.3.0src/Okta.Sdk.UnitTest/Okta.Sdk.UnitTest.csproj
NuGetRichardSzalay.MockHttp7.0.0src/Okta.Sdk.UnitTest/Okta.Sdk.UnitTest.csproj
NuGetWireMock.Net1.24.0src/Okta.Sdk.UnitTest/Okta.Sdk.UnitTest.csproj
NuGetxunit2.9.3src/Okta.Sdk.UnitTest/Okta.Sdk.UnitTest.csproj
NuGetxunit.runner.visualstudio3.1.5src/Okta.Sdk.UnitTest/Okta.Sdk.UnitTest.csproj
NuGetJsonSubTypes2.0.1src/Okta.Sdk/Okta.Sdk.csproj
NuGetNewtonsoft.Json13.0.3src/Okta.Sdk/Okta.Sdk.csproj
NuGetMicrosoft.Extensions.Configuration9.0.0src/Okta.Sdk/Okta.Sdk.csproj
NuGetOkta.Sdk.Abstractions4.0.4src/Okta.Sdk/Okta.Sdk.csproj
NuGetMicrosoft.Bcl.AsyncInterfaces9.0.0src/Okta.Sdk/Okta.Sdk.csproj
NuGetMicrosoft.IdentityModel.Tokens8.15.0src/Okta.Sdk/Okta.Sdk.csproj
NuGetMicrosoft.IdentityModel.Protocols8.15.0src/Okta.Sdk/Okta.Sdk.csproj
NuGetMicrosoft.IdentityModel.Protocols.OpenIdConnect8.15.0src/Okta.Sdk/Okta.Sdk.csproj
NuGetSystem.IdentityModel.Tokens.Jwt8.15.0src/Okta.Sdk/Okta.Sdk.csproj
NuGetSystem.Text.Json9.0.0src/Okta.Sdk/Okta.Sdk.csproj
NuGetRestSharp112.1.0src/Okta.Sdk/Okta.Sdk.csproj
NuGetPolly7.2.4src/Okta.Sdk/Okta.Sdk.csproj
All dependencies 27

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

RegistryPackageVersionRelation
NuGetcoverlet.collector6.0.4direct
NuGetcoverlet.msbuild6.0.4direct
NuGetFluentAssertions8.8.0direct
NuGetJsonSubTypes2.0.1direct
NuGetMicrosoft.Bcl.AsyncInterfaces9.0.0direct
NuGetMicrosoft.CSharp4.7.0direct
NuGetMicrosoft.Extensions.Configuration9.0.0direct
NuGetMicrosoft.IdentityModel.Protocols8.15.0direct
NuGetMicrosoft.IdentityModel.Protocols.OpenIdConnect8.15.0direct
NuGetMicrosoft.IdentityModel.Tokens8.15.0direct
NuGetMicrosoft.NET.Test.Sdk18.0.1direct
NuGetMoq4.20.72direct
NuGetNewtonsoft.Json13.0.3direct
NuGetNSubstitute5.3.0direct
NuGetOkta.Sdk.Abstractions4.0.4direct
NuGetPolly7.2.4direct
NuGetPolly8.6.5direct
NuGetRestSharp112.1.0direct
NuGetRichardSzalay.MockHttp7.0.0direct
NuGetSystem.IdentityModel.Tokens.Jwt8.15.0direct
NuGetSystem.Linq.Async—direct
NuGetSystem.Text.Json9.0.0direct
NuGetWireMock.Net1.24.0direct
NuGetxunit2.9.3direct
NuGetxunit.abstractions2.0.3direct
NuGetxunit.runner.visualstudio3.1.5direct
NuGetCake0.37.0indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 26 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 1 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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 — NuGet.