Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 04:15 UTC

Taritsyn / AutoprefixerHost

.NET wrapper around the Andrey Sitnik's Autoprefixer.

JavaScript · C#MIT★ 6 stars⑂ 2 forkssince Jul 2019View on GitHub ↗

Taritsyn/AutoprefixerHost holds a health index of 10 out of 100, placing it in the Critical band. It scores highest on Vitality (79/100) and lowest on Security (26/100). It was last updated today. A single contributor accounts for most of its recent work.

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

10
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 49 is calibrated to 48 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

Andrey TaritsynPersonal account
140 followers30 public repossince Apr 2010

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
NuGetAutoprefixerHost3.2.10-710 days agoautoprefixercss

Metrics by category

Vitality

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

79Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
6.2/36Commit cadence — 9/52 weeks with commits
13/18Commit volume — 27 commits in the last year
10/10OpenSSF Scorecard: Maintained — 13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year27
human_commit_share1
days_since_last_push0
active_weeks_last_year9

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 71 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~28.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count71
latest_release_tagv3.2.10
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases28.1
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
11.3/60Stars — 6 stars
0/25Forks — 2 forks
0/15Watchers — 0 watchers
Inputs used
forks2
stars6
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
57.2/80Total downloads — 322,578 downloads all-time across nuget
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesAutoprefixerHost
dependents—
ecosystemsnuget
total_downloads322,578
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?

51Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
42/42Issue resolution — 100% of issues closed
0/30PR acceptance — 0/1 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues2
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 backing — personal (user) account
0/20Verified domain — not applicable to user accounts
15.5/25Owner reach — 140 followers of Taritsyn
22.9/25Track record — 30 public repos, account ~16 yr old
Inputs used
followers140
owner_typeUser
is_verified—
owner_loginTaritsyn
public_repos30
account_age_days5,983
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

43Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsyes
has_editorconfigyes
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
0/10Topics
10/10Wiki
Inputs used
topics—
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?

26At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not 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_aggregate3.6
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier20
security_posture_after_multiplier7
security_posture_before_jurisdiction36
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 20% multiplier and gives Security posture an At risk ceiling of 34.

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_packages12
unassessed_packages12
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 12 resolved dependencies against OSV. 12 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.

27At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
1.1/40Legible commit history — 2 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.02
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — src/AutoprefixerHost/AutoprefixerHost.csproj, test/AutoprefixerHost.Benchmarks/AutoprefixerHost.Benchmarks.csproj, test/AutoprefixerHost.Tests/AutoprefixerHost.Tests.csproj (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
0/11Static type checking
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 — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestssrc/AutoprefixerHost/AutoprefixerHost.csproj, test/AutoprefixerHost.Benchmarks/AutoprefixerHost.Benchmarks.csproj, test/AutoprefixerHost.Tests/AutoprefixerHost.Tests.csproj
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
54.8/55Manageable file sizes — 1/286 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes155,867
source_files_sampled286
oversized_source_files1

Key facts

6GitHub stars
1contributors
27commits, last 12 months
0days since last push
71releases
1bus factor
0open issues
—package ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package 'AutoprefixerHost' from its registry

More detail

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

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.

111222212020-012020-032020-06
Major 0Minor 0Patch 4
OpenSSF Scorecard 3.6 / 10
3.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-09-12 04:15 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
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not 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
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
NuGetJavaScriptEngineSwitcher.Core3.31.0src/AutoprefixerHost/AutoprefixerHost.csproj
NuGetResxToCs.MSBuild1.0.0-alpha7src/AutoprefixerHost/AutoprefixerHost.csproj
NuGetNewtonsoft.Json13.0.4src/AutoprefixerHost/AutoprefixerHost.csproj
NuGetSystem.Text.Json4.7.2src/AutoprefixerHost/AutoprefixerHost.csproj
All dependencies 24

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

RegistryPackageVersionRelation
NuGetJavaScriptEngineSwitcher.Core3.31.0direct
NuGetNewtonsoft.Json13.0.4direct
NuGetResxToCs.MSBuild1.0.0-alpha7direct
NuGetSystem.Text.Json4.7.2direct
npm@babel/cli7.29.7indirect
npm@babel/core7.29.7indirect
npm@babel/preset-env7.29.7indirect
npmbootstrap5.3.8indirect
npmnormalize.css8.0.1indirect
npmreseter.css2.0.0indirect
npmskeleton.css2.0.4indirect
npmterser5.51.2indirect
NuGetBenchmarkDotNet—indirect
NuGetJavaScriptEngineSwitcher.ChakraCore—indirect
NuGetJavaScriptEngineSwitcher.ChakraCore.Native.linux-x64—indirect
NuGetJavaScriptEngineSwitcher.ChakraCore.Native.osx-x64—indirect
NuGetJavaScriptEngineSwitcher.ChakraCore.Native.win-x64—indirect
NuGetJavaScriptEngineSwitcher.ChakraCore.Native.win-x86—indirect
NuGetJavaScriptEngineSwitcher.Msie—indirect
NuGetJavaScriptEngineSwitcher.NiL—indirect
NuGetMicrosoft.NET.Test.Sdk—indirect
NuGetNUnit—indirect
NuGetNUnit3TestAdapter—indirect
NuGetSystem.Runtime.InteropServices.RuntimeInformation—indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 12 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 12 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.