Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 14:15 UTC

VahidN / EFCoreSecondLevelCacheInterceptor

EF Core Second Level Cache Interceptor

C#Apache-2.0★ 964 stars⑂ 105 forkssince Feb 2020View on GitHub ↗

VahidN/EFCoreSecondLevelCacheInterceptor holds a health index of 11 out of 100, placing it in the Critical band. It scores highest on Community & Adoption (69/100) and lowest on Security (10/100). It was last updated today. A single contributor accounts for most of its recent work.

11
overall / 100
Critical

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.

11
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 52 is calibrated to 53 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 20% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

Vahid NasiriPersonal account
1,180 followers79 public repossince May 2011

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?

62Moderate · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
11.1/36Commit cadence16/52 weeks with commits
14.9/18Commit volume45 commits in the last year
10/10OpenSSF Scorecard: Maintained28 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year45
human_commit_share
days_since_last_push0
active_weeks_last_year16
How it's scored
16.2/27Ships releases81 version tags (no GitHub releases)
0/36Release recencylatest release 877 days ago
27/27Release cadencea release every ~14 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count81
latest_release_tag4.2.2
releases_from_tagsyes
days_since_latest_release877
mean_days_between_releases14
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?

69Good · 17% of overall
How it's scored
48.4/60Stars964 stars
16.8/25Forks105 forks
7.6/15Watchers24 watchers
Inputs used
forks105
stars964
watchers24
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateyes
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes

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
4.1/22.5Commit distributiontop contributor authored 82% of commits
13.5/13.5Contributor breadth12 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled12
top_contributor_share0.818
How it's scored
42/42Issue resolution100% of issues closed
17.8/30PR acceptance70/118 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/26 approved changesets -- score normalized to 0
Inputs used
merged_prs70
open_issues0
closed_issues220
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs48
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
22.1/25Owner reach1,180 followers of VahidN
25/25Track record79 public repos, account ~15 yr old
Inputs used
followers1,180
owner_typeUser
is_verified
owner_loginVahidN
public_repos79
account_age_days5,553
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

62Moderate · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests1 out of 2 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsyes
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/10Topics6 topics
10/10Wiki
Inputs used
topicsaspnetcore, entity-framework, efcore, entityframework, entity-framework-core, ef-core
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?

10Critical · 16% of overall
How it's scored
3.8/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
1.2/2.5CI-Tests1 out of 2 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/26 approved changesets -- score normalized to 0
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
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.5Maintained28 commit(s) and 4 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
5/5SASTSAST tool is run on all commits
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_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.2
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier20
security_posture_after_multiplier10
security_posture_before_jurisdiction52
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 20% multiplier and gives Security posture an At risk ceiling of 34.

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.

38Weak · 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
22/22Automated tests
0/11Lint / format config
11/11Static type checkingC# (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeC# (statically typed)
54.6/55Manageable file sizes2/246 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes71,561
source_files_sampled246
oversized_source_files2

Key facts

964GitHub stars
12contributors
45commits, last 12 months
0days since last push
81releases
1bus factor
0open issues
package ecosystems

More detail

OpenSSF Scorecard 5.2 / 10
5.2aggregate

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 14:14 UTC

5Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
5CI-Tests1 out of 2 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/26 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
10Maintained28 commit(s) and 4 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
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 57

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

RegistryPackageVersionRelation
NuGetAsyncKeyedLockindirect
NuGetBenchmarkDotNetindirect
NuGetCacheManager.Coreindirect
NuGetCacheManager.Microsoft.Extensions.Caching.Memoryindirect
NuGetCacheManager.Serialization.Jsonindirect
NuGetCacheManager.StackExchange.Redisindirect
NuGetcoverlet.collectorindirect
NuGetEasyCaching.Bus.Redisindirect
NuGetEasyCaching.Coreindirect
NuGetEasyCaching.HybridCacheindirect
NuGetEasyCaching.InMemoryindirect
NuGetEasyCaching.Redisindirect
NuGetEasyCaching.Serialization.MessagePackindirect
NuGetEasyCaching.Serialization.SystemTextJsonindirect
NuGetEFCore.BulkExtensionsindirect
NuGetLamar.Microsoft.DependencyInjectionindirect
NuGetMessagePackindirect
NuGetMicrosoft.EntityFrameworkCoreindirect
NuGetMicrosoft.EntityFrameworkCore.Designindirect
NuGetMicrosoft.EntityFrameworkCore.InMemoryindirect
NuGetMicrosoft.EntityFrameworkCore.Relationalindirect
NuGetMicrosoft.EntityFrameworkCore.Sqliteindirect
NuGetMicrosoft.EntityFrameworkCore.Sqlite.Coreindirect
NuGetMicrosoft.EntityFrameworkCore.SqlServerindirect
NuGetMicrosoft.EntityFrameworkCore.SqlServer.NetTopologySuiteindirect
NuGetMicrosoft.EntityFrameworkCore.Toolsindirect
NuGetMicrosoft.Extensions.Caching.Hybridindirect
NuGetMicrosoft.Extensions.Caching.Memoryindirect
NuGetMicrosoft.Extensions.Caching.StackExchangeRedisindirect
NuGetMicrosoft.Extensions.Configurationindirect
NuGetMicrosoft.Extensions.Configuration.Abstractionsindirect
NuGetMicrosoft.Extensions.Configuration.Binderindirect
NuGetMicrosoft.Extensions.Configuration.FileExtensionsindirect
NuGetMicrosoft.Extensions.Configuration.Jsonindirect
NuGetMicrosoft.Extensions.DependencyInjection.Abstractionsindirect
NuGetMicrosoft.Extensions.Hostingindirect
NuGetMicrosoft.Extensions.Hosting.Abstractionsindirect
NuGetMicrosoft.Extensions.Loggingindirect
NuGetMicrosoft.Extensions.Logging.Consoleindirect
NuGetMicrosoft.Extensions.Logging.Debugindirect
NuGetMicrosoft.Extensions.Optionsindirect
NuGetMicrosoft.NET.Test.Sdkindirect
NuGetMicrosoft.SourceLink.GitHubindirect
NuGetMicrosoft.SqlServer.Typesindirect
NuGetMoqindirect
NuGetMSTest.TestAdapterindirect
NuGetMSTest.TestFrameworkindirect
NuGetMySql.EntityFrameworkCoreindirect
NuGetNewtonsoft.Jsonindirect
NuGetNpgsql.EntityFrameworkCore.PostgreSQLindirect
NuGetStackExchange.Redisindirect
NuGetSystem.Data.SqlClientindirect
NuGetSystem.IO.Hashingindirect
NuGetZiggyCreatures.FusionCacheindirect
NuGetZiggyCreatures.FusionCache.Backplane.StackExchangeRedisindirect
NuGetZiggyCreatures.FusionCache.Serialization.NewtonsoftJsonindirect
NuGetZiggyCreatures.FusionCache.Serialization.SystemTextJsonindirect
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.