Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 01:47 UTC

roblox-ts / types

TypeScript typings for the Roblox platform. Partially handwritten and partially automatically generated.

TypeScriptMIT★ 44 stars⑂ 83 forkssince Sep 2018View on GitHub ↗

roblox-ts/types holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Engineering Quality (79/100) and lowest on AI Readiness (50/100). It was last updated today. 2 contributors account for most of its recent work.

overall / 100

Good

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.

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

Ownership

roblox-tsOrganization

132 followers32 public repossince Sep 2018

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

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish	Tags
npm	@rbxts/types	1.0.950	18,656	742	0 days ago	types roblox typescript

Metrics by category

Vitality

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

57Moderate · 21% of overall

Development activity

94Exceptional

How it's scored

36/36	Push recency — last push 0 days ago
30.5/36	Commit cadence — 44/52 weeks with commits
17.3/18	Commit volume — 83 commits in the last year
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	83
human_commit_share	1
days_since_last_push	0
active_weeks_last_year	44

Release discipline

1Critical

How it's scored

0/27	Ships releases — no releases published
0/36	Release recency — no releases
0/27	Release cadence — no releases
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count

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

Popularity & adoption

44Weak

How it's scored

26.5/60	Stars — 44 stars
16/25	Forks — 83 forks
1.7/15	Watchers — 3 watchers

Inputs used

forks	83
stars	44
watchers	3
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	0
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	—
has_pull_request_template	no

Ecosystem adoption (downloads)

71Good

How it's scored

56.9/80	Monthly downloads — 18,656 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	@rbxts/types
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	18,656
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?

74Good · 23% of overall

Maintainer resilience (bus factor)

61Moderate

How it's scored

25.2/54	Bus factor — 2 contributor(s) cover half of all commits
12.7/22.5	Commit distribution — top contributor authored 43% of commits
13.5/13.5	Contributor breadth — 66 contributors
10/10	OpenSSF Scorecard: Contributors — project has 7 contributing companies or organizations

Inputs used

bus_factor	2
contributors_sampled	66
top_contributor_share	0.434

Issue & PR responsiveness

74Good

How it's scored

38.5/42	Issue resolution — 92% of issues closed
19/30	PR acceptance — 821/1,294 decided PRs merged
13/13	Newcomer PR acceptance — 2/2 first-time contributors' PRs merged in 30d
3/15	OpenSSF Scorecard: Code-Review — Found 7/30 approved changesets -- score normalized to 2

Inputs used

merged_prs	821
open_issues	9
closed_issues	99
prs_merged_7d	2
prs_decided_7d	3
prs_merged_30d	3
prs_decided_30d	5
issue_closed_ratio	0.917
closed_unmerged_prs	473
first_time_authors_30d	2
first_time_prs_merged_30d	2
first_time_prs_decided_30d	2

Ownership & stewardship

68Good

How it's scored

30/30	Ownership backing — organization-owned
0/20	Verified domain
15.3/25	Owner reach — 132 followers of roblox-ts
23.1/25	Track record — 32 public repos, account ~8 yr old

Inputs used

followers	132
owner_type	Organization
is_verified	no
owner_login	roblox-ts
public_repos	32
account_age_days	2,925

Package maintenance

100Exceptional

How it's scored

25/25	Published & resolvable — 1 package(s) on npm
35/35	Publish recency — latest publish 0 days ago
20/20	Version history — 742 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	@rbxts/types
ecosystems	npm
any_deprecated	no
min_days_since_publish	0

Engineering Quality

Are baseline engineering and documentation practices in place?

79Good · 19% of overall

Engineering practices

88Excellent

How it's scored

24/24	CI workflows — 4 workflow(s)
24/24	Tests present
16/16	Linter config — .eslintrc
0/9.6	Pre-commit hooks
6.4/6.4	.editorconfig
18/20	OpenSSF Scorecard: CI-Tests — 11 out of 12 merged PRs checked by a CI test -- score normalized to 9

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	yes
has_linter_config	yes
has_precommit_config	no

Documentation

65Good

How it's scored

30/30	README
0/25	Documentation directory
15/15	Documentation / homepage site — https://www.npmjs.com/package/@rbxts/types
10/10	Repository description
10/10	Topics — 1 topics
0/10	Wiki

Inputs used

topics	roblox-ts
has_wiki	no
homepage	https://www.npmjs.com/package/@rbxts/types
docs_site	https://www.npmjs.com/package/@rbxts/types
has_readme	yes
has_docs_dir	no
has_description	yes

Security

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

58Moderate · 16% of overall

Security posture

47Weak

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.2/2.5	CI-Tests — 11 out of 12 merged PRs checked by a CI test -- score normalized to 9
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5	Code-Review — Found 7/30 approved changesets -- score normalized to 2
2.5/2.5	Contributors — project has 7 contributing companies or organizations
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
5/5	Packaging — packaging workflow detected
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
0/7.5	Vulnerabilities — 20 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	17
scorecard_version	v5.5.0
checks_inconclusive	1
scorecard_aggregate	4.7

Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional

How it's scored

35/35	Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25	Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	28
affected_packages	10
assessed_packages	147
unassessed_packages	0
affected_by_severity	critical 1, high 7, moderate 2
direct_affected_packages	0

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 147 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.

50Moderate · 4% of overall

Agent context & guidance

13Critical

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15	Machine-readable docs (llms.txt)
12.8/40	Legible commit history — 24 of 100 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.24
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

59Moderate

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
11/11	Lint / format config — .eslintrc
11/11	Static type checking — include/tsconfig.json, tsconfig.json
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 100
5/8	Automated maintenance — dependency automation configured, none observed in the sampled commits
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	package-lock.json
has_dockerfile	no
typed_language	yes
bootstrap_files	—
has_devcontainer	no
has_linter_config	yes
typecheck_configs	include/tsconfig.json, tsconfig.json
agent_commit_share	0
toolchain_manifests	—
dependency_bot_commit_share	0

Code legibility for models

99Exceptional

How it's scored

45/45	Type-checkable code — TypeScript (statically typed)
53.6/55	Manageable file sizes — 1/39 source files over 60KB

Inputs used

primary_language	TypeScript
largest_source_bytes	123,099
source_files_sampled	39
oversized_source_files	1

Key facts

44GitHub stars

66contributors

83commits, last 12 months

0days since last push

0releases

2bus factor

9open issues

npmpackage ecosystems

Data collection warnings

Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 83 ⇿

0Stars

83Forks

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.

Each point covers 8 days.

OpenSSF Scorecard 4.7 / 10

4.7aggregate

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-09 01:47 UTC

10	Binary-Artifacts	no binaries found in the repo
0	Branch-Protection	branch protection not enabled on development/release branches
9	CI-Tests	11 out of 12 merged PRs checked by a CI test -- score normalized to 9
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
2	Code-Review	Found 7/30 approved changesets -- score normalized to 2
10	Contributors	project has 7 contributing companies or organizations
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
10	Packaging	packaging workflow 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
0	Vulnerabilities	20 existing vulnerabilities detected

Direct dependencies 3

Registry	Package	Version constraint	Manifest
npm	dom-serializer	`^2.0.0`	package.json
npm	domhandler	`^5.0.3`	package.json
npm	htmlparser2	`^10.0.0`	package.json

All dependencies 147

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

Registry	Package	Version	Relation
npm	dom-serializer	`2.0.0`	direct
npm	domhandler	`5.0.3`	direct
npm	htmlparser2	`10.0.0`	direct
npm	@aashutoshrathi/word-wrap	`1.2.6`	indirect
npm	@eslint-community/eslint-utils	`4.4.0`	indirect
npm	@eslint-community/regexpp	`4.10.1`	indirect
npm	@eslint/eslintrc	`2.1.4`	indirect
npm	@eslint/js	`8.57.0`	indirect
npm	@humanwhocodes/config-array	`0.11.14`	indirect
npm	@humanwhocodes/module-importer	`1.0.1`	indirect
npm	@humanwhocodes/object-schema	`2.0.2`	indirect
npm	@nodelib/fs.scandir	`2.1.5`	indirect
npm	@nodelib/fs.stat	`2.0.5`	indirect
npm	@nodelib/fs.walk	`1.2.8`	indirect
npm	@pkgr/core	`0.1.1`	indirect
npm	@rbxts/compiler-types	`3.0.0-types.0`	indirect
npm	@types/node	`22.13.10`	indirect
npm	@typescript-eslint/eslint-plugin	`7.18.0`	indirect
npm	@typescript-eslint/parser	`7.18.0`	indirect
npm	@typescript-eslint/scope-manager	`7.18.0`	indirect
npm	@typescript-eslint/type-utils	`7.18.0`	indirect
npm	@typescript-eslint/types	`7.18.0`	indirect
npm	@typescript-eslint/typescript-estree	`7.18.0`	indirect
npm	@typescript-eslint/utils	`7.18.0`	indirect
npm	@typescript-eslint/visitor-keys	`7.18.0`	indirect
npm	@ungap/structured-clone	`1.2.0`	indirect
npm	acorn	`8.11.3`	indirect
npm	acorn-jsx	`5.3.2`	indirect
npm	ajv	`6.12.6`	indirect
npm	ansi-regex	`5.0.1`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	argparse	`2.0.1`	indirect
npm	array-union	`2.1.0`	indirect
npm	balanced-match	`1.0.0`	indirect
npm	brace-expansion	`1.1.11`	indirect
npm	brace-expansion	`2.0.1`	indirect
npm	braces	`3.0.3`	indirect
npm	callsites	`3.1.0`	indirect
npm	chalk	`4.1.0`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	concat-map	`0.0.1`	indirect
npm	cross-spawn	`7.0.3`	indirect
npm	debug	`4.3.4`	indirect
npm	deep-is	`0.1.4`	indirect
npm	dir-glob	`3.0.1`	indirect
npm	doctrine	`3.0.0`	indirect
npm	domelementtype	`2.3.0`	indirect
npm	domutils	`3.2.2`	indirect
npm	entities	`4.5.0`	indirect
npm	entities	`6.0.0`	indirect
npm	escape-string-regexp	`4.0.0`	indirect
npm	eslint	`8.57.0`	indirect
npm	eslint-config-prettier	`10.1.1`	indirect
npm	eslint-plugin-no-autofix	`2.1.0`	indirect
npm	eslint-plugin-prettier	`5.2.3`	indirect
npm	eslint-plugin-simple-import-sort	`12.1.1`	indirect
npm	eslint-rule-composer	`0.3.0`	indirect
npm	eslint-scope	`7.2.2`	indirect
npm	eslint-visitor-keys	`3.4.3`	indirect
npm	espree	`9.6.1`	indirect
npm	esquery	`1.5.0`	indirect
npm	esrecurse	`4.3.0`	indirect
npm	estraverse	`5.2.0`	indirect
npm	estraverse	`5.3.0`	indirect
npm	esutils	`2.0.3`	indirect
npm	fast-deep-equal	`3.1.3`	indirect
npm	fast-diff	`1.2.0`	indirect
npm	fast-glob	`3.3.2`	indirect
npm	fast-json-stable-stringify	`2.1.0`	indirect
npm	fast-levenshtein	`2.0.6`	indirect
npm	fastq	`1.8.0`	indirect
npm	file-entry-cache	`6.0.1`	indirect
npm	fill-range	`7.1.1`	indirect
npm	find-up	`5.0.0`	indirect
npm	flat-cache	`3.0.4`	indirect
npm	flatted	`3.2.5`	indirect
npm	fs.realpath	`1.0.0`	indirect
npm	glob	`7.1.6`	indirect
npm	glob-parent	`5.1.2`	indirect
npm	glob-parent	`6.0.2`	indirect
npm	globals	`13.24.0`	indirect
npm	globby	`11.1.0`	indirect
npm	graphemer	`1.4.0`	indirect
npm	has-flag	`4.0.0`	indirect
npm	ignore	`5.3.1`	indirect
npm	import-fresh	`3.3.0`	indirect
npm	imurmurhash	`0.1.4`	indirect
npm	inflight	`1.0.6`	indirect
npm	inherits	`2.0.4`	indirect
npm	is-extglob	`2.1.1`	indirect
npm	is-glob	`4.0.3`	indirect
npm	is-number	`7.0.0`	indirect
npm	is-path-inside	`3.0.3`	indirect
npm	isexe	`2.0.0`	indirect
npm	js-yaml	`4.1.0`	indirect
npm	json-schema-traverse	`0.4.1`	indirect
npm	json-stable-stringify-without-jsonify	`1.0.1`	indirect
npm	levn	`0.4.1`	indirect
npm	locate-path	`6.0.0`	indirect
npm	lodash.merge	`4.6.2`	indirect
npm	merge2	`1.4.1`	indirect
npm	micromatch	`4.0.4`	indirect
npm	minimatch	`3.1.2`	indirect
npm	minimatch	`9.0.5`	indirect
npm	ms	`2.1.2`	indirect
npm	natural-compare	`1.4.0`	indirect
npm	once	`1.4.0`	indirect
npm	optionator	`0.9.3`	indirect
npm	p-limit	`3.1.0`	indirect
npm	p-locate	`5.0.0`	indirect
npm	parent-module	`1.0.1`	indirect
npm	path-exists	`4.0.0`	indirect
npm	path-is-absolute	`1.0.1`	indirect
npm	path-key	`3.1.1`	indirect
npm	path-type	`4.0.0`	indirect
npm	picomatch	`2.3.1`	indirect
npm	prelude-ls	`1.2.1`	indirect
npm	prettier	`3.5.3`	indirect
npm	prettier-linter-helpers	`1.0.0`	indirect
npm	punycode	`2.3.1`	indirect
npm	queue-microtask	`1.2.3`	indirect
npm	resolve-from	`4.0.0`	indirect
npm	reusify	`1.0.4`	indirect
npm	rimraf	`3.0.2`	indirect
npm	run-parallel	`1.2.0`	indirect
npm	semver	`7.6.2`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.0.0`	indirect
npm	slash	`3.0.0`	indirect
npm	strip-ansi	`6.0.1`	indirect
npm	strip-json-comments	`3.1.1`	indirect
npm	supports-color	`7.2.0`	indirect
npm	synckit	`0.9.2`	indirect
npm	text-table	`0.2.0`	indirect
npm	to-regex-range	`5.0.1`	indirect
npm	ts-api-utils	`1.3.0`	indirect
npm	ts-expose-internals	`5.6.3`	indirect
npm	tslib	`2.8.1`	indirect
npm	type-check	`0.4.0`	indirect
npm	type-fest	`0.20.2`	indirect
npm	typescript	`5.7.3`	indirect
npm	undici-types	`6.20.0`	indirect
npm	uri-js	`4.4.1`	indirect
npm	which	`2.0.2`	indirect
npm	wrappy	`1.0.2`	indirect
npm	yocto-queue	`0.1.0`	indirect

Dependency advisories 10

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

Package	Version	Relation	Severity	Advisories	Fixed in
flatted	`3.2.5`	indirect	critical	2	`3.4.2`
brace-expansion	`1.1.11`	indirect	high	5	`5.0.9`
brace-expansion	`2.0.1`	indirect	high	5	`5.0.9`
cross-spawn	`7.0.3`	indirect	high	1	`7.0.5`
js-yaml	`4.1.0`	indirect	high	5	`4.3.2`
minimatch	`3.1.2`	indirect	high	3	`10.2.3`
minimatch	`9.0.5`	indirect	high	3	`10.2.3`
picomatch	`2.3.1`	indirect	high	2	`4.0.4`
ajv	`6.12.6`	indirect	moderate	1	`8.18.0`
micromatch	`4.0.4`	indirect	moderate	1	`4.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.

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.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records