Public recordGood
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 23:28 UTC
junkurihara / jscu
JavaScript cryptographic utilities for crypto-suite compatibility including PEM/X509/JWK converter.
junkurihara/jscu holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Engineering Quality (86/100) and lowest on AI Readiness (42/100). It was last updated today. A single contributor accounts for most of its recent work.
67
overall / 100Software 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.
67
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)
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 61 is calibrated to 67 on the published index scale (record calibration 2026-08-02).
Ownership
Jun KuriharaPersonal account
127 followers164 public repossince Nov 2014Science Tokyo, and Zettant Inc.
This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish | Tags |
|---|---|---|---|---|---|---|
| npm | js-crypto-ec | 1.0.7 | 17,731 | 46 | 1078 days ago | cryptoelliptic-curvewebcryptoecdsaecdh |
| npm | js-crypto-aes | 1.0.6 | 39,782 | 38 | 1078 days ago | cryptoaeswebcrypto |
| npm | js-crypto-env | 1.0.5 | 220,678 | 19 | 1078 days ago | jscu |
| npm | js-crypto-rsa | 1.0.7 | 16,879 | 48 | 1078 days ago | cryptowebcryptorsarsa-oaeprsa-pssrsassa-pkcs1-v1-5rfc3447 |
| npm | js-x509-utilspoints to another repo — not scored | 1.0.7 | 13,448 | 49 | 1078 days ago | cryptox509certificaterfc5280 |
| npm | js-crypto-hash | 1.0.7 | 64,112 | 36 | 1078 days ago | cryptohashwebcrypto |
| npm | js-crypto-hkdf | 1.0.7 | 39,547 | 41 | 1078 days ago | cryptohkdfrfc5869webcrypto |
| npm | js-crypto-hmac | 1.0.7 | 63,977 | 39 | 1078 days ago | cryptohmacwebcrypto |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
54
Development activity
50Moderate
How it's scored
| 36/36 | Push recency — last push 0 days ago |
| 2.7/36 | Commit cadence — 52/52 weeks with commits, discounted for automation: 3 of the last 100 commits human-authored, spanning 145 days |
| 1.3/18 | Commit volume — 243 commits in the last year, discounted for automation: 3 of the last 100 commits human-authored, spanning 145 days |
| 10/10 | OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
Inputs used
| commits_last_year | 243 |
| human_commit_share | 0.03 |
| days_since_last_push | 0 |
| active_weeks_last_year | 52 |
Release discipline
60Moderate
How it's scored
| 27/27 | Ships releases — 2 releases published |
| 0/36 | Release recency — latest release 1,078 days ago |
| 27/27 | Release cadence — a release every ~3.5 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 2 |
| latest_release_tag | v1.0.7 |
| releases_from_tags | no |
| days_since_latest_release | 1,078 |
| mean_days_between_releases | 3.5 |
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?
60
Popularity & adoption
48Weak
How it's scored
| 35.8/60 | Stars — 162 stars |
| 10/25 | Forks — 17 forks |
| 2.7/15 | Watchers — 4 watchers |
Inputs used
| forks | 17 |
| stars | 162 |
| watchers | 4 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
50Moderate
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (MIT) |
| 0/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | yes |
| readme_badges | 4 |
| has_contributing | no |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | api.codeclimate.com, codecov.io, github.com, shields.io |
| has_pull_request_template | no |
Ecosystem adoption (downloads)
94Exceptional
How it's scored
| 75.5/80 | Monthly downloads — 462,706 downloads/month across npm |
| 0/20 | Registry dependents — not reported by this ecosystem |
Inputs used
| packages | js-crypto-ec, js-crypto-aes, js-crypto-env, js-crypto-rsa, js-crypto-hash, js-crypto-hkdf, js-crypto-hmac |
| dependents | — |
| ecosystems | npm |
| total_downloads | — |
| monthly_downloads | 462,706 |
| 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?
56
Maintainer resilience (bus factor)
26At Risk
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 5.2/22.5 | Commit distribution — top contributor authored 77% of commits |
| 5.4/13.5 | Contributor breadth — 4 contributors |
| 6/10 | OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6 |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 4 |
| top_contributor_share | 0.769 |
How it's scored
| 35.5/42 | Issue resolution — 85% of issues closed |
| 29.8/30 | PR acceptance — 2,171/2,185 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — Found 0/25 approved changesets -- score normalized to 0 |
Inputs used
| merged_prs | 2,171 |
| open_issues | 4 |
| closed_issues | 22 |
| prs_merged_7d | 0 |
| prs_decided_7d | 0 |
| prs_merged_30d | 0 |
| prs_decided_30d | 0 |
| issue_closed_ratio | 0.846 |
| closed_unmerged_prs | 14 |
| first_time_authors_30d | 0 |
| first_time_prs_merged_30d | 0 |
| first_time_prs_decided_30d | 0 |
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
Ownership & stewardship
63Moderate
How it's scored
| 10/30 | Ownership backing — personal (user) account |
| 0/20 | Verified domain — not applicable to user accounts |
| 15.1/25 | Owner reach — 127 followers of junkurihara |
| 25/25 | Track record — 164 public repos, account ~11 yr old |
Inputs used
| followers | 127 |
| owner_type | User |
| is_verified | — |
| owner_login | junkurihara |
| public_repos | 164 |
| account_age_days | 4,321 |
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
Package maintenance
69Good
How it's scored
| 25/25 | Published & resolvable — 7 package(s) on npm |
| 4/35 | Publish recency — latest publish 1,078 days ago |
| 20/20 | Version history — 48 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | js-crypto-ec, js-crypto-aes, js-crypto-env, js-crypto-rsa, js-crypto-hash, js-crypto-hkdf, js-crypto-hmac |
| ecosystems | npm |
| any_deprecated | no |
| min_days_since_publish | 1,078 |
Engineering Quality
Are baseline engineering and documentation practices in place?
86
Engineering practices
84Excellent
How it's scored
| 24/24 | CI workflows — 1 workflow(s) |
| 24/24 | Tests present |
| 16/16 | Linter config — .eslintrc.json |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 20/20 | OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10 |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | yes |
| has_precommit_config | no |
Documentation
90Excellent
How it's scored
| 30/30 | README |
| 25/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://junkurihara.github.io/jscu-webpage/ |
| 10/10 | Repository description |
| 0/10 | Topics |
| 10/10 | Wiki |
Inputs used
| topics | — |
| has_wiki | yes |
| homepage | https://junkurihara.github.io/jscu-webpage/ |
| docs_site | https://junkurihara.github.io/jscu-webpage/ |
| has_readme | yes |
| has_docs_dir | yes |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
55
Security posture
50Moderate
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — branch protection not enabled on development/release branches |
| 2.5/2.5 | CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10 |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 0/7.5 | Code-Review — Found 0/25 approved changesets -- score normalized to 0 |
| 1.5/2.5 | Contributors — project has 2 contributing companies or organizations -- score normalized to 6 |
| 10/10 | Dangerous-Workflow — no dangerous workflow patterns detected |
| 7.5/7.5 | Dependency-Update-Tool — update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 7.5/7.5 | Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| 0/5 | Packaging — no data |
| 0/5 | Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
| 0/5 | SAST — SAST tool is not run on all commits -- score normalized to 0 |
| 0/5 | Security-Policy — security policy file not detected |
| 0/7.5 | Signed-Releases — no data |
| 0/7.5 | Token-Permissions — detected GitHub workflow tokens with excessive permissions |
| 7.5/7.5 | Vulnerabilities — 0 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 16 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 2 |
| scorecard_aggregate | 5 |
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
Dependency advisories
73Good
How it's scored
| 14/35 | Direct dependencies free of known advisories — 1 affected: elliptic 6.5.7 (high 7.5) |
| 25/25 | Indirect dependencies free of known advisories — no indirect dependency carries a known advisory |
| 33.7/40 | No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 694 days ago |
Inputs used
| source | osv |
| advisories | 3 |
| affected_packages | 1 |
| assessed_packages | 28 |
| unassessed_packages | 0 |
| affected_by_severity | high 1 |
| direct_affected_packages | 1 |
Matched the npm:js-crypto-ec@1.0.7 runtime dependency closure — what installing the published package pulls in — 28 packages. 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.
42
Agent context & guidance
1Critical
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 0/40 | Legible commit history — no data |
Inputs used
| has_llms_txt | no |
| 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.
Verify loop (build / test / typecheck)
52Moderate
How it's scored
| 0/18 | One-command bootstrap |
| 22/22 | Automated tests |
| 11/11 | Lint / format config — .eslintrc.json |
| 11/11 | Static type checking — packages/js-crypto-aes/tsconfig.json, packages/js-crypto-ec/tsconfig.json, packages/js-crypto-env/tsconfig.json, packages/js-crypto-hash/tsconfig.json, packages/js-crypto-hkdf/tsconfig.json, packages/js-crypto-hmac/tsconfig.json, packages/js-crypto-key-utils/tsconfig.json, packages/js-crypto-pbkdf/tsconfig.json, packages/js-crypto-random/tsconfig.json, packages/js-crypto-rsa/tsconfig.json, packages/js-crypto-utils/tsconfig.json, packages/js-x509-utils/tsconfig.json |
| 0/10 | Reproducible environment |
| 0/10 | Demonstrated agent practice — no agent-authored commits among the last 100 |
| 8/8 | Automated maintenance — 97 of the last 100 commits are automated dependency updates |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | — |
| has_dockerfile | no |
| typed_language | yes |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | yes |
| typecheck_configs | packages/js-crypto-aes/tsconfig.json, packages/js-crypto-ec/tsconfig.json, packages/js-crypto-env/tsconfig.json, packages/js-crypto-hash/tsconfig.json, packages/js-crypto-hkdf/tsconfig.json, packages/js-crypto-hmac/tsconfig.json, packages/js-crypto-key-utils/tsconfig.json, packages/js-crypto-pbkdf/tsconfig.json, packages/js-crypto-random/tsconfig.json, packages/js-crypto-rsa/tsconfig.json, packages/js-crypto-utils/tsconfig.json, packages/js-x509-utils/tsconfig.json |
| agent_commit_share | 0 |
| toolchain_manifests | — |
| dependency_bot_commit_share | 0.97 |
Code legibility for models
100Exceptional
How it's scored
| 45/45 | Type-checkable code — TypeScript (statically typed) |
| 55/55 | Manageable file sizes — 0/207 source files over 60KB |
Inputs used
| primary_language | TypeScript |
| largest_source_bytes | 21,292 |
| source_files_sampled | 207 |
| oversized_source_files | 0 |
Key facts
162GitHub stars
4contributors
243commits, last 12 months
0days since last push
2releases
1bus factor
4open issues
npmpackage ecosystems
Data collection warnings
- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
- npm package 'js-x509-utils' points at a different repository (https://github.com/junkurihara/js-x509-utils); excluded from ecosystem scoring
More detail
Star and fork history 0 ★ / 17 ⇿
0Stars
17Forks
2Releases
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.
Major 0Minor 0Patch 2
Each point covers 7 days.
OpenSSF Scorecard 5.0 / 10
5.0aggregate
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).
| 10 | Binary-Artifacts | no binaries found in the repo |
| 0 | Branch-Protection | branch protection not enabled on development/release branches |
| 10 | CI-Tests | 30 out of 30 merged PRs checked by a CI test -- score normalized to 10 |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 0 | Code-Review | Found 0/25 approved changesets -- score normalized to 0 |
| 6 | Contributors | project has 2 contributing companies or organizations -- score normalized to 6 |
| 10 | Dangerous-Workflow | no dangerous workflow patterns detected |
| 10 | Dependency-Update-Tool | update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 10 | Maintained | 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| n/a | Packaging | packaging workflow not detected |
| 0 | Pinned-Dependencies | dependency not pinned by hash detected -- score normalized to 0 |
| 0 | SAST | SAST tool is not run on all commits -- score normalized to 0 |
| 0 | Security-Policy | security policy file not detected |
| n/a | Signed-Releases | no releases found |
| 0 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 10 | Vulnerabilities | 0 existing vulnerabilities detected |
Direct dependencies 63
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| npm | js-crypto-env | ^1.0.5 | packages/js-crypto-aes/package.json |
| npm | asn1.js | ~5.4.1 | packages/js-crypto-ec/package.json |
| npm | buffer | ~6.0.0 | packages/js-crypto-ec/package.json |
| npm | elliptic | ~6.6.0 | packages/js-crypto-ec/package.json |
| npm | js-crypto-env | ^1.0.5 | packages/js-crypto-ec/package.json |
| npm | js-crypto-hash | ^1.0.7 | packages/js-crypto-ec/package.json |
| npm | js-crypto-key-utils | ^1.0.7 | packages/js-crypto-ec/package.json |
| npm | js-crypto-random | ^1.0.5 | packages/js-crypto-ec/package.json |
| npm | js-encoding-utils | 0.7.3 | packages/js-crypto-ec/package.json |
| npm | buffer | ~6.0.0 | packages/js-crypto-hash/package.json |
| npm | hash.js | ~1.1.7 | packages/js-crypto-hash/package.json |
| npm | js-crypto-env | ^1.0.5 | packages/js-crypto-hash/package.json |
| npm | md5 | ~2.3.0 | packages/js-crypto-hash/package.json |
| npm | sha3 | ~2.1.0 | packages/js-crypto-hash/package.json |
| npm | js-crypto-env | ^1.0.5 | packages/js-crypto-hkdf/package.json |
| npm | js-crypto-hash | ^1.0.7 | packages/js-crypto-hkdf/package.json |
| npm | js-crypto-hmac | ^1.0.7 | packages/js-crypto-hkdf/package.json |
| npm | js-crypto-random | ^1.0.5 | packages/js-crypto-hkdf/package.json |
| npm | js-encoding-utils | 0.7.3 | packages/js-crypto-hkdf/package.json |
| npm | js-crypto-env | ^1.0.5 | packages/js-crypto-hmac/package.json |
| npm | js-crypto-hash | ^1.0.7 | packages/js-crypto-hmac/package.json |
| npm | asn1.js | ~5.4.1 | packages/js-crypto-key-utils/package.json |
| npm | buffer | 6.0.3 | packages/js-crypto-key-utils/package.json |
| npm | des.js | ~1.1.0 | packages/js-crypto-key-utils/package.json |
| npm | elliptic | 6.6.1 | packages/js-crypto-key-utils/package.json |
| npm | js-crypto-aes | ^1.0.6 | packages/js-crypto-key-utils/package.json |
| npm | js-crypto-hash | ^1.0.7 | packages/js-crypto-key-utils/package.json |
| npm | js-crypto-pbkdf | ^1.0.7 | packages/js-crypto-key-utils/package.json |
| npm | js-crypto-random | ^1.0.5 | packages/js-crypto-key-utils/package.json |
| npm | js-encoding-utils | 0.7.3 | packages/js-crypto-key-utils/package.json |
| npm | lodash.clonedeep | ~4.5.0 | packages/js-crypto-key-utils/package.json |
| npm | js-crypto-hash | ^1.0.7 | packages/js-crypto-pbkdf/package.json |
| npm | js-crypto-hmac | ^1.0.7 | packages/js-crypto-pbkdf/package.json |
| npm | js-encoding-utils | 0.7.3 | packages/js-crypto-pbkdf/package.json |
| npm | js-crypto-env | ^1.0.5 | packages/js-crypto-random/package.json |
| npm | bn.js | ~5.2.2 | packages/js-crypto-rsa/package.json |
| npm | buffer | ~6.0.3 | packages/js-crypto-rsa/package.json |
| npm | js-crypto-env | ^1.0.5 | packages/js-crypto-rsa/package.json |
| npm | js-crypto-hash | ^1.0.7 | packages/js-crypto-rsa/package.json |
| npm | js-crypto-key-utils | ^1.0.7 | packages/js-crypto-rsa/package.json |
| npm | js-crypto-random | ^1.0.5 | packages/js-crypto-rsa/package.json |
| npm | js-encoding-utils | 0.7.3 | packages/js-crypto-rsa/package.json |
| npm | js-crypto-aes | ^1.0.6 | packages/js-crypto-utils/package.json |
| npm | js-crypto-ec | ^1.0.7 | packages/js-crypto-utils/package.json |
| npm | js-crypto-hash | ^1.0.7 | packages/js-crypto-utils/package.json |
| npm | js-crypto-hkdf | ^1.0.7 | packages/js-crypto-utils/package.json |
| npm | js-crypto-hmac | ^1.0.7 | packages/js-crypto-utils/package.json |
| npm | js-crypto-key-utils | ^1.0.7 | packages/js-crypto-utils/package.json |
| npm | js-crypto-pbkdf | ^1.0.7 | packages/js-crypto-utils/package.json |
| npm | js-crypto-random | ^1.0.5 | packages/js-crypto-utils/package.json |
| npm | js-crypto-rsa | ^1.0.7 | packages/js-crypto-utils/package.json |
| npm | js-encoding-utils | 0.7.3 | packages/js-crypto-utils/package.json |
| npm | js-x509-utils | ^1.0.7 | packages/js-crypto-utils/package.json |
| npm | lodash.clonedeep | ~4.5.0 | packages/js-crypto-utils/package.json |
| npm | asn1.js | ~5.4.1 | packages/js-x509-utils/package.json |
| npm | asn1.js-rfc5280 | ~3.0.0 | packages/js-x509-utils/package.json |
| npm | bn.js | ~5.2.0 | packages/js-x509-utils/package.json |
| npm | buffer | ~6.0.0 | packages/js-x509-utils/package.json |
| npm | js-crypto-ec | ^1.0.7 | packages/js-x509-utils/package.json |
| npm | js-crypto-key-utils | ^1.0.7 | packages/js-x509-utils/package.json |
| npm | js-crypto-random | ^1.0.5 | packages/js-x509-utils/package.json |
| npm | js-crypto-rsa | ^1.0.7 | packages/js-x509-utils/package.json |
| npm | js-encoding-utils | 0.7.3 | packages/js-x509-utils/package.json |
All dependencies 52
Full resolved dependency set from the GitHub dependency graph: 26 direct and 26 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|---|---|---|
| npm | asn1.js | ~5.4.1 | direct |
| npm | asn1.js-rfc5280 | ~3.0.0 | direct |
| npm | bn.js | ~5.2.0 | direct |
| npm | bn.js | ~5.2.2 | direct |
| npm | buffer | 6.0.3 | direct |
| npm | buffer | ~6.0.0 | direct |
| npm | buffer | ~6.0.3 | direct |
| npm | des.js | ~1.1.0 | direct |
| npm | elliptic | 6.6.1 | direct |
| npm | elliptic | ~6.6.0 | direct |
| npm | hash.js | ~1.1.7 | direct |
| npm | js-crypto-aes | ^1.0.6 | direct |
| npm | js-crypto-ec | ^1.0.7 | direct |
| npm | js-crypto-env | ^1.0.5 | direct |
| npm | js-crypto-hash | ^1.0.7 | direct |
| npm | js-crypto-hkdf | ^1.0.7 | direct |
| npm | js-crypto-hmac | ^1.0.7 | direct |
| npm | js-crypto-key-utils | ^1.0.7 | direct |
| npm | js-crypto-pbkdf | ^1.0.7 | direct |
| npm | js-crypto-random | ^1.0.5 | direct |
| npm | js-crypto-rsa | ^1.0.7 | direct |
| npm | js-encoding-utils | 0.7.3 | direct |
| npm | js-x509-utils | ^1.0.7 | direct |
| npm | lodash.clonedeep | ~4.5.0 | direct |
| npm | md5 | ~2.3.0 | direct |
| npm | sha3 | ~2.1.0 | direct |
| npm | @types/bn.js | 5.2.0 | indirect |
| npm | @types/elliptic | 6.4.18 | indirect |
| npm | @types/jest | 30.0.0 | indirect |
| npm | @types/lodash.clonedeep | 4.5.9 | indirect |
| npm | @types/node | 25.9.5 | indirect |
| npm | @typescript-eslint/eslint-plugin | 8.70.0 | indirect |
| npm | @typescript-eslint/parser | 8.70.0 | indirect |
| npm | @vitest/browser | 5.0.0 | indirect |
| npm | @vitest/browser-playwright | 5.0.0 | indirect |
| npm | @vitest/coverage-v8 | 5.0.0 | indirect |
| npm | @vitest/ui | 5.0.0 | indirect |
| npm | can-npm-publish | 1.3.6 | indirect |
| npm | cross-env | 10.1.0 | indirect |
| npm | esdoc | 1.1.0 | indirect |
| npm | esdoc-standard-plugin | 1.0.0 | indirect |
| npm | eslint | 10.10.0 | indirect |
| npm | glob | 13.0.6 | indirect |
| npm | jest | 30.4.2 | indirect |
| npm | lerna | 10.0.1 | indirect |
| npm | playwright | 1.63.0 | indirect |
| npm | ts-jest | 29.4.12 | indirect |
| npm | ts-loader | 9.6.2 | indirect |
| npm | typescript | 7.0.2 | indirect |
| npm | vitest | 5.0.0 | indirect |
| npm | webpack | 5.110.3 | indirect |
| npm | webpack-cli | 7.2.3 | indirect |
Dependency advisories 1
Installing npm:js-crypto-ec@1.0.7 pulls in 28 packages, direct and transitive: 1 carry known advisories, of which 1 are direct dependencies.
| Package | Version | Relation | Severity | Advisories | Fixed in |
|---|---|---|---|---|---|
| elliptic | 6.5.7 | direct | high | 3 | 6.6.1 |
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.
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 — npm.