Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 11:35 UTC

stdlib-js / string-from-code-point

Create a string from a sequence of Unicode code points.

JavaScriptApache-2.0★ 2 stars⑂ 0 forkssince Jun 2021View on GitHub ↗

stdlib-js/string-from-code-point holds a health index of 62 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (89/100) and lowest on Security (41/100). It was last updated today. A single contributor accounts for most of its recent work.

62
overall / 100
Moderate

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.

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

Ownership

stdlibOrganization
289 followers5,851 public repossince Mar 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@stdlib/string-from-code-point0.2.361,00414159 days agostdlibstdstringstringstrutilitiesutilityutilsutilcodepointptunicodeutf-16utf16

Metrics by category

Vitality

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

59Moderate · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
4.2/36Commit cadence6/52 weeks with commits
7.6/18Commit volume6 commits in the last year
3/10OpenSSF Scorecard: Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year6
human_commit_share
days_since_last_push0
active_weeks_last_year6
How it's scored
16.2/27Ships releases30 version tags (no GitHub releases)
27/36Release recencylatest release 159 days ago
19.8/27Release cadencea release every ~62.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count30
latest_release_tagv0.2.3-cli
releases_from_tagsyes
days_since_latest_release159
mean_days_between_releases62.2
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?

53Moderate · 17% of overall
How it's scored
0/60Stars2 stars
0/25Forks0 forks
0/15Watchers2 watchers
Inputs used
forks0
stars2
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
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_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateyes
How it's scored
63.8/80Monthly downloads61,004 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@stdlib/string-from-code-point
dependents
ecosystemsnpm
total_downloads
monthly_downloads61,004
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?

47Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolutionno issues or no data
0/30PR acceptanceno decided pull requests or no data
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs0
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
17.7/25Owner reach289 followers of stdlib-js
25/25Track record5,851 public repos, account ~10 yr old
Inputs used
followers289
owner_typeOrganization
is_verified
owner_loginstdlib-js
public_repos5,851
account_age_days3,778
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 159 days ago
20/20Version history14 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@stdlib/string-from-code-point
ecosystemsnpm
any_deprecatedno
min_days_since_publish159

Engineering Quality

Are baseline engineering and documentation practices in place?

89Excellent · 19% of overall
How it's scored
24/24CI workflows13 workflow(s)
24/24Tests present
16/16Linter config.eslintrc.js
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://github.com/stdlib-js/stdlib
10/10Repository description
10/10Topics17 topics
0/10Wiki
Inputs used
topicsnodejs, javascript, stdlib, node, node-js, string, str, utilities, utility, utils, util, code, point, pt, unicode, utf-16, utf16
has_wikino
homepagehttps://github.com/stdlib-js/stdlib
docs_sitehttps://github.com/stdlib-js/stdlib
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

41Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 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
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
2.2/7.5Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
0/5Packagingno data
2/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
0/5SASTno SAST tool detected
4.5/5Security-Policysecurity policy file 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_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.1
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, Signed-Releases. Remaining weights renormalized.

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.

50Moderate · 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
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format config.eslintrc.js
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
4/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/11 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes6,974
source_files_sampled11
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

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

More detail

OpenSSF Scorecard 4.1 / 10
4.1aggregate

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 11:35 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
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
3Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
n/aPackagingpackaging workflow not detected
4Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
0SASTno SAST tool detected
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 13
RegistryPackageVersion constraintManifest
npm@stdlib/assert-is-collection^0.2.3package.json
npm@stdlib/assert-is-nonnegative-integer^0.2.3package.json
npm@stdlib/cli-ctor^0.2.3package.json
npm@stdlib/constants-unicode-max^0.2.3package.json
npm@stdlib/constants-unicode-max-bmp^0.2.3package.json
npm@stdlib/fs-read-file^0.2.3package.json
npm@stdlib/process-read-stdin^0.2.3package.json
npm@stdlib/regexp-eol^0.2.3package.json
npm@stdlib/streams-node-stdin^0.2.3package.json
npm@stdlib/string-format^0.2.3package.json
npm@stdlib/types^0.5.1package.json
npm@stdlib/utils-regexp-from-string^0.2.3package.json
npm@stdlib/error-tools-fmtprodmsg^0.2.3package.json
All dependencies 26

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

RegistryPackageVersionRelation
npm@stdlib/assert-is-collection^0.2.3direct
npm@stdlib/assert-is-nonnegative-integer^0.2.3direct
npm@stdlib/cli-ctor^0.2.3direct
npm@stdlib/constants-unicode-max^0.2.3direct
npm@stdlib/constants-unicode-max-bmp^0.2.3direct
npm@stdlib/error-tools-fmtprodmsg^0.2.3direct
npm@stdlib/fs-read-file^0.2.3direct
npm@stdlib/process-read-stdin^0.2.3direct
npm@stdlib/regexp-eol^0.2.3direct
npm@stdlib/streams-node-stdin^0.2.3direct
npm@stdlib/string-format^0.2.3direct
npm@stdlib/types^0.5.1direct
npm@stdlib/utils-regexp-from-string^0.2.3direct
npm@stdlib/array-float64^0.2.3indirect
npm@stdlib/array-uint16^0.2.3indirect
npm@stdlib/assert-is-browser^0.2.3indirect
npm@stdlib/assert-is-string^0.2.3indirect
npm@stdlib/assert-is-windows^0.2.3indirect
npm@stdlib/bench-harness^0.2.3indirect
npm@stdlib/math-base-special-floor^0.2.4indirect
npm@stdlib/math-base-special-pow^0.3.1indirect
npm@stdlib/process-exec-path^0.2.3indirect
npm@stdlib/random-base-randu^0.2.3indirect
npm@stdlib/string-replace^0.2.3indirect
npmistanbul^0.4.1indirect
npmproxyquire^2.0.0indirect
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 statisticsnpm.