Software health reportschema 0.27.0 · metrics 2.5.0 · 2026-08-01 11:24 UTC

stacksjs / ts-videos

📹 Make your videos load faster. A better save for the web.

TypeScriptMIT★ 4 stars⑂ 1 forksince Jan 2025View on GitHub ↗

#cli #ffmpeg #library #typescript #video #web-optimized #video-compression #video-converter

stacksjs/ts-videos holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Vitality (86/100) and lowest on Sustainability & Governance (45/100). It was last updated today. A single contributor accounts 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 65 is calibrated to 75 on the published index scale (record calibration 2026-08-02).

Ownership

StacksOrganization

119 followers153 public repossince Sep 2022

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	@ts-videos/ts	0.1.1	310	2	9 days ago	mpeg-ts transport-stream ts video streaming typescript zero-dependency
npm	@ts-videos/mp4	0.1.1	4,683	2	9 days ago	mp4 mov isobmff video audio codec demuxer muxer
npm	@ts-videos/webm	0.1.1	4,687	2	9 days ago	webm matroska mkv video audio codec ebml
npm	ts-videos	0.1.1	5,561	2	9 days ago	video audio media codec demuxer muxer mp4 webm typescript zero-dependency

Metrics by category

Vitality

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

86Excellent · 21% of overall

Development activity

76Good

How it's scored

36/36	Push recency — last push 0 days ago
13.2/36	Commit cadence — 19/52 weeks with commits
17/18	Commit volume — 78 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	78
human_commit_share	0.988
days_since_last_push	0
active_weeks_last_year	19

Release discipline

100Exceptional

How it's scored

27/27	Ships releases — 2 releases published
36/36	Release recency — latest release 9 days ago
27/27	Release cadence — a release every ~0 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	2
latest_release_tag	v0.1.1
releases_from_tags	no
days_since_latest_release	9
mean_days_between_releases	0

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?

50Moderate · 17% of overall

Popularity & adoption

8Critical

How it's scored

7.7/60	Stars — 4 stars
0/25	Forks — 1 forks
0/15	Watchers — 1 watchers

Inputs used

forks	1
stars	4
watchers	1
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

85Excellent

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
18/18	CONTRIBUTING guide
13.5/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	—
has_contributing	yes
has_issue_template	no
has_code_of_conduct	yes
readme_badge_services	—
has_pull_request_template	no

Ecosystem adoption (downloads)

70Good

How it's scored

55.8/80	Monthly downloads — 15,241 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	@ts-videos/ts, @ts-videos/mp4, @ts-videos/webm, ts-videos
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	15,241

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?

45Weak · 23% of overall

Maintainer resilience (bus factor)

32At Risk

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
8/22.5	Commit distribution — top contributor authored 64% of commits
5.4/13.5	Contributor breadth — 4 contributors
10/10	OpenSSF Scorecard: Contributors — project has 11 contributing companies or organizations

Inputs used

bus_factor	1
contributors_sampled	4
top_contributor_share	0.643

Issue & PR responsiveness

1Critical

How it's scored

0/42	Issue resolution — 0% of issues closed
0/30	PR acceptance — 1/994 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/30 approved changesets -- score normalized to 0

Inputs used

merged_prs	1
open_issues	4
closed_issues	0
prs_merged_7d	—
prs_decided_7d	—
prs_merged_30d	—
prs_decided_30d	—
issue_closed_ratio	0
closed_unmerged_prs	993
first_time_authors_30d	—
first_time_prs_merged_30d	—
first_time_prs_decided_30d	—

Excluded from scoring (no data or not applicable): newcomer_pr_acceptance. Remaining weights renormalized.

Ownership & stewardship

66Good

How it's scored

30/30	Ownership backing — organization-owned
0/20	Verified domain
14.9/25	Owner reach — 119 followers of stacksjs
20.7/25	Track record — 153 public repos, account ~3 yr old

Inputs used

followers	119
owner_type	Organization
is_verified	—
owner_login	stacksjs
public_repos	153
account_age_days	1,401

Package maintenance

92Excellent

How it's scored

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

Inputs used

packages	@ts-videos/ts, @ts-videos/mp4, @ts-videos/webm, ts-videos
ecosystems	npm
any_deprecated	no
min_days_since_publish	9

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall

Engineering practices

68Good

How it's scored

24/24	CI workflows — 3 workflow(s)
24/24	Tests present
0/16	Linter config
0/9.6	Pre-commit hooks
6.4/6.4	.editorconfig
0/20	OpenSSF Scorecard: CI-Tests — no data

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	yes
has_linter_config	no
has_precommit_config	no

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

90Excellent

How it's scored

30/30	README
25/25	Documentation directory
15/15	Documentation / homepage site — https://stacks-vidx.netlify.app
10/10	Repository description
10/10	Topics — 8 topics
0/10	Wiki

Inputs used

topics	cli, ffmpeg, library, typescript, video, web-optimized, video-compression, video-converter
has_wiki	no
homepage	https://stacks-vidx.netlify.app
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?

64Moderate · 16% of overall

Security posture

55Moderate

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
0/2.5	CI-Tests — no data
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5	Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5	Contributors — project has 11 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
0/5	Packaging — no data
0/5	Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5	SAST — no SAST tool detected
5/5	Security-Policy — security policy file detected
0/7.5	Signed-Releases — no data
0/7.5	Token-Permissions — detected GitHub workflow tokens with excessive permissions
6.8/7.5	Vulnerabilities — 1 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	15
scorecard_version	v5.5.0
checks_inconclusive	3
scorecard_aggregate	5.5

Excluded from scoring (no data or not applicable): ci_tests, packaging, 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
25/25	Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	0
affected_packages	0
assessed_packages	5
unassessed_packages	0
affected_by_severity	none
direct_affected_packages	0

Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:ts-videos@0.1.1 runtime dependency closure — what installing the published package pulls in — 5 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.

71Good · 4% of overall

Agent context & guidance

85Excellent

How it's scored

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

Inputs used

has_llms_txt	no
legible_history_share	1
agent_instruction_files	CLAUDE.md
agent_instruction_max_bytes	1,352

Verify loop (build / test / typecheck)

51Moderate

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
0/11	Lint / format config
11/11	Static type checking — tsconfig.json
0/10	Reproducible environment
10/10	Demonstrated agent practice — 7 of the last 85 commits agent-authored or agent-credited
8/8	Automated maintenance — 1 of the last 85 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	no
typecheck_configs	tsconfig.json
agent_commit_share	0.082
toolchain_manifests	—
dependency_bot_commit_share	0.012

Code legibility for models

99Exceptional

How it's scored

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

Inputs used

primary_language	TypeScript
largest_source_bytes	63,731
source_files_sampled	77
oversized_source_files	1

Key facts

4GitHub stars

4contributors

78commits, 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

More detail

OpenSSF Scorecard 5.5 / 10

5.5aggregate

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-08-01 11:24 UTC

10	Binary-Artifacts	no binaries found in the repo
0	Branch-Protection	branch protection not enabled on development/release branches
n/a	CI-Tests	no pull request found
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
0	Code-Review	Found 0/30 approved changesets -- score normalized to 0
10	Contributors	project has 11 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
n/a	Packaging	packaging workflow not detected
0	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 0
0	SAST	no SAST tool detected
10	Security-Policy	security policy file detected
n/a	Signed-Releases	no releases found
0	Token-Permissions	detected GitHub workflow tokens with excessive permissions
9	Vulnerabilities	1 existing vulnerabilities detected

Direct dependencies 1

Registry	Package	Version constraint	Manifest
npm	bunfig	`^0.15.6`	packages/ts-videos/package.json

All dependencies 5

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

Registry	Package	Version	Relation
npm	bunfig	`^0.15.6`	direct
npm	@stacksjs/clapp	`^0.2.0`	indirect
npm	better-dx	`^0.2.15`	indirect
npm	better-dx	`^0.2.5`	indirect
npm	bun-plugin-dtsx	`^0.9.9`	indirect

Dependency advisories 0

Installing npm:ts-videos@0.1.1 pulls in 5 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

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

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.5.0, schema v0.27.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

Related records