Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-04 23:07 UTC

OpenCut-app / OpenCut

The open-source CapCut alternative

TypeScript · RustMIT★ 80,925 stars⑂ 8,026 forkssince Jun 2025View on GitHub ↗
KindWeb interfacehow this is determined

OpenCut-app/OpenCut holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Vitality (86/100) and lowest on Security (43/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

OpenCut.appOrganization
934 followers4 public repossince Jun 2025

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

Metrics by category

Vitality

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

86Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
20.1/36Commit cadence29/52 weeks with commits
18/18Commit volume524 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year524
human_commit_share1
days_since_last_push0
active_weeks_last_year29
How it's scored
27/27Ships releases3 releases published
27/36Release recencylatest release 111 days ago
27/27Release cadencea release every ~25.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count3
latest_release_tagv0.3.0
releases_from_tagsno
days_since_latest_release111
mean_days_between_releases25.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?

86Excellent · 17% of overall
How it's scored
60/60Stars80,925 stars
25/25Forks8,026 forks
14.3/15Watchers375 watchers
Inputs used
forks8,026
stars80,925
watchers375
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
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateyes

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

46Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
7/22.5Commit distributiontop contributor authored 69% of commits
13.5/13.5Contributor breadth97 contributors
10/10OpenSSF Scorecard: Contributorsproject has 28 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled97
top_contributor_share0.687
How it's scored
11.2/42Issue resolution27% of issues closed
15.2/30PR acceptance192/380 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs192
open_issues264
closed_issues96
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d1
issue_closed_ratio0.267
closed_unmerged_prs188
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
21.4/25Owner reach934 followers of OpenCut-app
7.3/25Track record4 public repos, account ~1 yr old
Inputs used
followers934
owner_typeOrganization
is_verified
owner_loginOpenCut-app
public_repos4
account_age_days408
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

48Weak · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://opencut.app
10/10Repository description
10/10Topics3 topics
10/10Wiki
Inputs used
topicseditor, oss, videoeditor
has_wikiyes
homepagehttps://opencut.app
docs_sitehttps://opencut.app
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

43Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3.8/7.5Branch-Protectionbranch protection is not maximal on development and all 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
2.5/2.5Contributorsproject has 28 contributing companies or organizations
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
7.5/7.5Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTno SAST tool detected
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities11 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.3
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.

66Good · 4% of overall
How it's scored
45/45Agent instructions.github/copilot-instructions.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history95 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.95
agent_instruction_files.github/copilot-instructions.md
agent_instruction_max_bytes17,109
How it's scored
12.6/18One-command bootstrapCargo.toml, apps/desktop/Cargo.toml (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checkingapps/web/tsconfig.json
10/10Reproducible environmentlockfile
6/10Demonstrated agent practice3 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfilesCargo.lock
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configsapps/web/tsconfig.json
agent_commit_share0.03
toolchain_manifestsCargo.toml, apps/desktop/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/80 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes21,914
source_files_sampled80
oversized_source_files0

Key facts

80,925GitHub stars
97contributors
524commits, last 12 months
0days since last push
3releases
1bus factor
264open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'opencut-desktop' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 8,026 ⇿
0Stars
8,026Forks

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

7,0007,2007,4007,6007,8008,0008,2008,0261362026-072026-072026-08
OpenSSF Scorecard 4.3 / 10
4.3aggregate

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-04 23:07 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all 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
10Contributorsproject has 28 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities11 existing vulnerabilities detected
Direct dependencies 37
RegistryPackageVersion constraintManifest
npmelysialatestapps/api/package.json
crates.iogpuiapps/desktop/Cargo.toml
npm@base-ui/react^1.4.1apps/web/package.json
npm@cloudflare/vite-plugin^1.26.0apps/web/package.json
npm@fontsource-variable/inter^5.2.8apps/web/package.json
npm@hookform/resolvers^5.2.2apps/web/package.json
npm@hugeicons/core-free-icons^4.1.2apps/web/package.json
npm@hugeicons/react^1.1.6apps/web/package.json
npm@tailwindcss/vite^4.1.18apps/web/package.json
npm@tanstack/react-devtoolslatestapps/web/package.json
npm@tanstack/react-routerlatestapps/web/package.json
npm@tanstack/react-router-devtoolslatestapps/web/package.json
npm@tanstack/react-router-ssr-querylatestapps/web/package.json
npm@tanstack/react-startlatestapps/web/package.json
npm@tanstack/router-plugin^1.132.0apps/web/package.json
npmclass-variance-authority^0.7.1apps/web/package.json
npmclsx^2.1.1apps/web/package.json
npmcmdk^1.1.1apps/web/package.json
npmdate-fns^4.1.0apps/web/package.json
npmembla-carousel-react^8.6.0apps/web/package.json
npminput-otp^1.4.2apps/web/package.json
npmlucide-react^1.14.0apps/web/package.json
npmnext-themes^0.4.6apps/web/package.json
npmradix-ui^1.4.3apps/web/package.json
npmreact^19.2.0apps/web/package.json
npmreact-day-picker^10.0.0apps/web/package.json
npmreact-dom^19.2.0apps/web/package.json
npmreact-hook-form^7.75.0apps/web/package.json
npmreact-resizable-panels^4.11.0apps/web/package.json
npmrecharts3.8.0apps/web/package.json
npmshadcn^4.7.0apps/web/package.json
npmsonner^2.0.7apps/web/package.json
npmtailwind-merge^3.5.0apps/web/package.json
npmtailwindcss^4.1.18apps/web/package.json
npmtw-animate-css^1.4.0apps/web/package.json
npmvaul^1.1.2apps/web/package.json
npmzod^4.4.3apps/web/package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics.