Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 05:40 UTC

bad4iz / crypto-pro-cadesplugin

JavaScript-библиотека для работы с сертификатами и создания электронной подписи через «КриптоПро ЭЦП Browser plug-in».

JavaScriptMIT★ 13 stars⑂ 5 forkssince Apr 2021View on GitHub ↗

bad4iz/crypto-pro-cadesplugin holds a health index of 8 out of 100, placing it in the Critical band. It scores highest on Sustainability & Governance (65/100) and lowest on AI Readiness (16/100). It was last updated 29 days ago. A single contributor accounts for most of its recent work.

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

8
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 42 is calibrated to 38 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

Eugene PlotnikovPersonal account
29 followers143 public repossince Jan 2016

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

Package ecosystems

Metrics by category

Vitality

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

56Moderate · 21% of overall
How it's scored
28.8/36Push recencylast push 29 days ago
1.4/36Commit cadence2/52 weeks with commits
7.6/18Commit volume6 commits in the last year
0/10OpenSSF Scorecard: Maintainedno data
Inputs used
commits_last_year6
human_commit_share1
days_since_last_push29
active_weeks_last_year2
How it's scored
27/27Ships releases3 releases published
36/36Release recencylatest release 29 days ago
5.4/27Release cadencea release every ~472 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count3
latest_release_tagv1.2.0
releases_from_tagsno
days_since_latest_release29
mean_days_between_releases472

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

41Weak · 17% of overall
How it's scored
17.5/60Stars13 stars
5/25Forks5 forks
0/15Watchers1 watchers
Inputs used
forks5
stars13
watchers1
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_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io, travis-ci.com
has_pull_request_templateno
How it's scored
46.5/80Monthly downloads3,096 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagescrypto-pro-cadesplugin
dependents
ecosystemsnpm
total_downloads
monthly_downloads3,096
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?

65Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
5/22.5Commit distributiontop contributor authored 78% of commits
4.1/13.5Contributor breadth3 contributors
0/10OpenSSF Scorecard: Contributorsno data
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.778
How it's scored
42/42Issue resolution100% of issues closed
30/30PR acceptance4/4 decided PRs merged
13/13Newcomer PR acceptance2/2 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Reviewno data
Inputs used
merged_prs4
open_issues0
closed_issues3
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio1
closed_unmerged_prs0
first_time_authors_30d1
first_time_prs_merged_30d2
first_time_prs_decided_30d2
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
10.6/25Owner reach29 followers of bad4iz
25/25Track record143 public repos, account ~10 yr old
Inputs used
followers29
owner_typeUser
is_verified
owner_loginbad4iz
public_repos143
account_age_days3,887
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 29 days ago
20/20Version history26 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagescrypto-pro-cadesplugin
ecosystemsnpm
any_deprecatedno
min_days_since_publish29

Engineering Quality

Are baseline engineering and documentation practices in place?

21At Risk · 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
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

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?

21At Risk · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfilespublished library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilespackage-lock.json, yarn.lock
manifestspackage.json
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier20
security_posture_after_multiplier1
security_posture_before_jurisdiction1
Excluded from scoring (no data or not applicable): Dependency lockfiles. 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 advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories24
affected_packages11
assessed_packages233
unassessed_packages0
affected_by_severitycritical 2, high 7, moderate 2
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 233 resolved dependencies against OSV. 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.

16Critical · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
3.4/40Legible commit history5 of 79 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.063
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 79
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json, yarn.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/12 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes29,799
source_files_sampled12
oversized_source_files0

Key facts

13GitHub stars
3contributors
6commits, last 12 months
29days since last push
3releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/bad4iz/crypto-pro-cadesplugin: run: RepoClient.LocalPath: error during tarballHandler.setup: internal error: handler.httpClient.Do: Get "https://codeload.github.com/bad4iz/crypto-pro-cadesplugin/legacy.tar.gz/refs/heads/main": internal error: innerTransport.RoundTrip: internal error: innerTransport.RoundTrip: error in HTTP: dial tcp: lookup codeload.github.com on 127.0.0.11:53: server misbehaving); skipping Scorecard checks

More detail

Star and fork history 0 ★ / 5 ⇿
0Stars
5Forks
1Releases

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.

12345512023-022024-032025-05
Major 0Minor 1Patch 0

Each point covers 3 days.

All dependencies 233

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

RegistryPackageVersionRelation
npm@oxc-project/types0.146.0indirect
npm@rolldown/binding-android-arm-eabi1.2.5indirect
npm@rolldown/binding-android-arm641.2.5indirect
npm@rolldown/binding-darwin-arm641.2.5indirect
npm@rolldown/binding-darwin-x641.2.5indirect
npm@rolldown/binding-freebsd-x641.2.5indirect
npm@rolldown/binding-linux-arm-gnueabihf1.2.5indirect
npm@rolldown/binding-linux-arm64-gnu1.2.5indirect
npm@rolldown/binding-linux-arm64-musl1.2.5indirect
npm@rolldown/binding-linux-ppc64-gnu1.2.5indirect
npm@rolldown/binding-linux-s390x-gnu1.2.5indirect
npm@rolldown/binding-linux-x64-gnu1.2.5indirect
npm@rolldown/binding-linux-x64-musl1.2.5indirect
npm@rolldown/binding-openharmony-arm641.2.5indirect
npm@rolldown/binding-win32-arm64-msvc1.2.5indirect
npm@rolldown/binding-win32-x64-msvc1.2.5indirect
npm@rolldown/pluginutils1.0.1indirect
npmansi-regex2.1.1indirect
npmansi-styles2.2.1indirect
npmanymatch1.3.2indirect
npmarr-diff2.0.0indirect
npmarr-diff4.0.0indirect
npmarr-flatten1.1.0indirect
npmarr-union3.1.0indirect
npmarray-unique0.2.1indirect
npmarray-unique0.3.2indirect
npmassign-symbols1.0.0indirect
npmasync-each1.0.3indirect
npmatob2.1.2indirect
npmbabel-cli6.26.0indirect
npmbabel-code-frame6.26.0indirect
npmbabel-core6.26.3indirect
npmbabel-generator6.26.1indirect
npmbabel-helpers6.24.1indirect
npmbabel-messages6.23.0indirect
npmbabel-plugin-transform-es2015-modules-commonjs6.26.2indirect
npmbabel-plugin-transform-strict-mode6.24.1indirect
npmbabel-polyfill6.26.0indirect
npmbabel-register6.26.0indirect
npmbabel-runtime6.26.0indirect
npmbabel-template6.26.0indirect
npmbabel-traverse6.26.0indirect
npmbabel-types6.26.0indirect
npmbabylon6.18.0indirect
npmbalanced-match1.0.2indirect
npmbase0.11.2indirect
npmbinary-extensions1.13.1indirect
npmbindings1.5.0indirect
npmbrace-expansion1.1.11indirect
npmbraces1.8.5indirect
npmbraces2.3.2indirect
npmcache-base1.0.1indirect
npmchalk1.1.3indirect
npmchokidar1.7.0indirect
npmclass-utils0.3.6indirect
npmcollection-visit1.0.0indirect
npmcommander2.20.3indirect
npmcomponent-emitter1.3.0indirect
npmconcat-map0.0.1indirect
npmconvert-source-map1.8.0indirect
npmcopy-descriptor0.1.1indirect
npmcore-js2.6.11indirect
npmcore-js2.6.12indirect
npmcore-util-is1.0.2indirect
npmdebug2.6.9indirect
npmdecode-uri-component0.2.0indirect
npmdefine-property0.2.5indirect
npmdefine-property1.0.0indirect
npmdefine-property2.0.2indirect
npmdetect-indent4.0.0indirect
npmdetect-libc2.1.2indirect
npmescape-string-regexp1.0.5indirect
npmesutils2.0.3indirect
npmexpand-brackets0.1.5indirect
npmexpand-brackets2.1.4indirect
npmexpand-range1.8.2indirect
npmextend-shallow2.0.1indirect
npmextend-shallow3.0.2indirect
npmextglob0.3.2indirect
npmextglob2.0.4indirect
npmfdir6.5.0indirect
npmfile-uri-to-path1.0.0indirect
npmfilename-regex2.0.1indirect
npmfill-range2.2.4indirect
npmfill-range4.0.0indirect
npmfor-in1.0.2indirect
npmfor-own0.1.5indirect
npmfragment-cache0.2.1indirect
npmfs-readdir-recursive1.1.0indirect
npmfs.realpath1.0.0indirect
npmfsevents1.2.13indirect
npmfsevents2.3.3indirect
npmget-value2.0.6indirect
npmglob7.1.7indirect
npmglob-base0.3.0indirect
npmglob-parent2.0.0indirect
npmglobals9.18.0indirect
npmgraceful-fs4.2.8indirect
npmhas-ansi2.0.0indirect
npmhas-value0.3.1indirect
npmhas-value1.0.0indirect
npmhas-values0.1.4indirect
npmhas-values1.0.0indirect
npmhome-or-tmp2.0.0indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npminvariant2.2.4indirect
npmis-accessor-descriptor0.1.6indirect
npmis-accessor-descriptor1.0.0indirect
npmis-binary-path1.0.1indirect
npmis-buffer1.1.6indirect
npmis-data-descriptor0.1.4indirect
npmis-data-descriptor1.0.0indirect
npmis-descriptor0.1.6indirect
npmis-descriptor1.0.2indirect
npmis-dotfile1.0.3indirect
npmis-equal-shallow0.1.3indirect
npmis-extendable0.1.1indirect
npmis-extendable1.0.1indirect
npmis-extglob1.0.0indirect
npmis-finite1.1.0indirect
npmis-glob2.0.1indirect
npmis-number2.1.0indirect
npmis-number3.0.0indirect
npmis-number4.0.0indirect
npmis-plain-object2.0.4indirect
npmis-posix-bracket0.1.1indirect
npmis-primitive2.0.0indirect
npmis-windows1.0.2indirect
npmisarray1.0.0indirect
npmisobject2.1.0indirect
npmisobject3.0.1indirect
npmjs-tokens3.0.2indirect
npmjs-tokens4.0.0indirect
npmjsesc1.3.0indirect
npmjson50.5.1indirect
npmkind-of3.2.2indirect
npmkind-of4.0.0indirect
npmkind-of5.1.0indirect
npmkind-of6.0.3indirect
npmlightningcss1.33.0indirect
npmlightningcss-android-arm641.33.0indirect
npmlightningcss-darwin-arm641.33.0indirect
npmlightningcss-darwin-x641.33.0indirect
npmlightningcss-freebsd-x641.33.0indirect
npmlightningcss-linux-arm-gnueabihf1.33.0indirect
npmlightningcss-linux-arm64-gnu1.33.0indirect
npmlightningcss-linux-arm64-musl1.33.0indirect
npmlightningcss-linux-x64-gnu1.33.0indirect
npmlightningcss-linux-x64-musl1.33.0indirect
npmlightningcss-win32-arm64-msvc1.33.0indirect
npmlightningcss-win32-x64-msvc1.33.0indirect
npmlodash4.17.15indirect
npmloose-envify1.4.0indirect
npmmap-cache0.2.2indirect
npmmap-visit1.0.0indirect
npmmath-random1.0.4indirect
npmmicromatch2.3.11indirect
npmmicromatch3.1.10indirect
npmminimatch3.0.4indirect
npmminimist1.2.5indirect
npmmixin-deep1.3.2indirect
npmmkdirp0.5.5indirect
npmms2.0.0indirect
npmnan2.15.0indirect
npmnanoid3.3.18indirect
npmnanomatch1.2.13indirect
npmnormalize-path2.1.1indirect
npmobject-assign4.1.1indirect
npmobject-copy0.1.0indirect
npmobject-visit1.0.1indirect
npmobject.omit2.0.1indirect
npmobject.pick1.3.0indirect
npmonce1.4.0indirect
npmos-homedir1.0.2indirect
npmos-tmpdir1.0.2indirect
npmoutput-file-sync1.1.2indirect
npmparse-glob3.0.4indirect
npmpascalcase0.1.1indirect
npmpath-is-absolute1.0.1indirect
npmpicocolors1.1.1indirect
npmpicomatch4.0.5indirect
npmposix-character-classes0.1.1indirect
npmpostcss8.5.26indirect
npmpreserve0.2.0indirect
npmprivate0.1.8indirect
npmprocess-nextick-args2.0.1indirect
npmrandomatic3.1.1indirect
npmreadable-stream2.3.7indirect
npmreaddirp2.2.1indirect
npmregenerator-runtime0.10.5indirect
npmregenerator-runtime0.11.1indirect
npmregex-cache0.4.4indirect
npmregex-not1.0.2indirect
npmremove-trailing-separator1.1.0indirect
npmrepeat-element1.1.4indirect
npmrepeat-string1.6.1indirect
npmrepeating2.0.1indirect
npmresolve-url0.2.1indirect
npmret0.1.15indirect
npmrolldown1.2.5indirect
npmsafe-buffer5.1.2indirect
npmsafe-regex1.1.0indirect
npmset-value2.0.1indirect
npmslash1.0.0indirect
npmsnapdragon0.8.2indirect
npmsnapdragon-node2.1.1indirect
npmsnapdragon-util3.0.1indirect
npmsource-map0.5.7indirect
npmsource-map-js1.2.1indirect
npmsource-map-resolve0.5.3indirect
npmsource-map-support0.4.18indirect
npmsource-map-url0.4.1indirect
npmsplit-string3.1.0indirect
npmstatic-extend0.1.2indirect
npmstring_decoder1.1.1indirect
npmstrip-ansi3.0.1indirect
npmsupports-color2.0.0indirect
npmtinyglobby0.2.17indirect
npmto-fast-properties1.0.3indirect
npmto-object-path0.3.0indirect
npmto-regex3.0.2indirect
npmto-regex-range2.1.1indirect
npmtrim-right1.0.1indirect
npmunion-value1.0.1indirect
npmunset-value1.0.0indirect
npmurix0.1.0indirect
npmuse3.1.1indirect
npmuser-home1.1.1indirect
npmutil-deprecate1.0.2indirect
npmv8flags2.1.1indirect
npmvite8.2.2indirect
npmwrappy1.0.2indirect
Dependency advisories 11

This repository publishes no package the index resolves, so its own dependency graph was assessed — 233 packages, which also include development and test pins that never ship: 11 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
babel-traverse6.26.0indirectcritical18.0.0-alpha.4
minimist1.2.5indirectcritical11.2.6
brace-expansion1.1.11indirecthigh55.0.9
braces1.8.5indirecthigh13.0.3
braces2.3.2indirecthigh13.0.3
decode-uri-component0.2.0indirecthigh20.5.0
json50.5.1indirecthigh12.2.2
lodash4.17.15indirecthigh64.18.0
minimatch3.0.4indirecthigh410.2.3
micromatch2.3.11indirectmoderate14.0.8
micromatch3.1.10indirectmoderate14.0.8

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