Public record
Software health reportschema 0.30.0 · metrics 2.10.0 · 2026-08-04 09:12 UTC

m7md1alaa / stdout-design

local-first studio that renders your own TSX components into finished social/marketing images

TypeScriptMIT★ 2 stars⑂ 0 forkssince Jun 2026View on GitHub ↗
KindCommand-line toolWeb interfaceLibraryhow this is determined

m7md1alaa/stdout-design holds a health index of 62 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (77/100) and lowest on Community & Adoption (35/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

Mohammed alaaPersonal account
34 followers24 public repossince Jun 2021

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

Metrics by category

Vitality

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

75Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
3.5/36Commit cadence5/52 weeks with commits
18/18Commit volume116 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year116
human_commit_share1
days_since_last_push0
active_weeks_last_year5

Release discipline

100Exceptional
How it's scored
27/27Ships releases14 releases published
36/36Release recencylatest release 10 days ago
27/27Release cadencea release every ~0.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count14
latest_release_tagv0.3.2
releases_from_tagsno
days_since_latest_release10
mean_days_between_releases0.1
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?

35Weak · 17% of overall
How it's scored
0/60Stars2 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars2
watchers0
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
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
54.6/80Monthly downloads12,481 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@stdout-design/cli, @stdout-design/core, @stdout-design/web-ui, @stdout-design/dev-server
dependents
ecosystemsnpm
total_downloads
monthly_downloads12,481
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?

54Moderate · 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
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolutionno issues or no data
30/30PR acceptance2/2 decided PRs merged
13/13Newcomer PR acceptance2/2 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/8 approved changesets -- score normalized to 0
Inputs used
merged_prs2
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio
closed_unmerged_prs0
first_time_authors_30d1
first_time_prs_merged_30d2
first_time_prs_decided_30d2
Excluded from scoring (no data or not applicable): Issue resolution. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
11.1/25Owner reach34 followers of m7md1alaa
20.5/25Track record24 public repos, account ~5 yr old
Inputs used
followers34
owner_typeUser
is_verified
owner_loginm7md1alaa
public_repos24
account_age_days1,878
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable4 package(s) on npm
35/35Publish recencylatest publish 10 days ago
20/20Version history24 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@stdout-design/cli, @stdout-design/core, @stdout-design/web-ui, @stdout-design/dev-server
ecosystemsnpm
any_deprecatedno
min_days_since_publish10

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests2 out of 2 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://stdout-design-web-docs.vercel.app
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepagehttps://stdout-design-web-docs.vercel.app
docs_sitehttps://stdout-design-web-docs.vercel.app
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

39Weak · 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
2.5/2.5CI-Tests2 out of 2 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/8 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
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
0/7.5Maintainedproject was created within the last 90 days. Please review its contents carefully
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities20 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate2.4
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages35
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:@stdout-design/cli@0.3.2 runtime dependency closure — what installing the published package pulls in — 35 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.

69Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes5,410
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingapps/web-docs/tsconfig.json, examples/tsconfig.json, packages/cli/template/tsconfig.json, packages/cli/tsconfig.json, packages/core/tsconfig.json, packages/dev-server/tsconfig.json, packages/web-ui/tsconfig.json, tsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
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_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configsapps/web-docs/tsconfig.json, examples/tsconfig.json, packages/cli/template/tsconfig.json, packages/cli/tsconfig.json, packages/core/tsconfig.json, packages/dev-server/tsconfig.json, packages/web-ui/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/179 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes34,271
source_files_sampled179
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
116commits, last 12 months
0days since last push
14releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 2.4 / 10
2.4aggregate

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 09:12 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests2 out of 2 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/8 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities20 existing vulnerabilities detected
Direct dependencies 46
RegistryPackageVersion constraintManifest
npmdotenv^17.4.2package.json
npm@fumadocs/base-ui^16.13.0apps/web-docs/package.json
npm@orama/orama^3.1.18apps/web-docs/package.json
npm@stdout-design/coreworkspace:*apps/web-docs/package.json
npm@takumi-rs/core^2.1.1apps/web-docs/package.json
npmclass-variance-authority^0.7.1apps/web-docs/package.json
npmclsx^2.1.1apps/web-docs/package.json
npmfumadocs-core16.12.1apps/web-docs/package.json
npmfumadocs-mdx15.2.0apps/web-docs/package.json
npmfumadocs-uinpm:@fumadocs/base-ui@16.12.1apps/web-docs/package.json
npmlucide-react^1.28.0apps/web-docs/package.json
npmnext16.2.11apps/web-docs/package.json
npmreact^19.2.8apps/web-docs/package.json
npmreact-dom^19.2.8apps/web-docs/package.json
npmshadcn^4.16.0apps/web-docs/package.json
npmtailwind-merge^3.6.0apps/web-docs/package.json
npmtakumi-js^2.1.1apps/web-docs/package.json
npmtw-animate-css^1.4.0apps/web-docs/package.json
npm@clack/prompts^1.7.0packages/cli/package.json
npm@stdout-design/coreworkspace:*packages/cli/package.json
npmcommander^15.0.0packages/cli/package.json
npmpackage-manager-detector^1.8.0packages/cli/package.json
npm@takumi-rs/core^2.1.1packages/core/package.json
npm@takumi-rs/helpers^2.1.1packages/core/package.json
npmcsv-parse^7.0.1packages/core/package.json
npmkysely^0.29.3packages/core/package.json
npmp-limit^7.3.0packages/core/package.json
npmproper-lockfile^4.1.2packages/core/package.json
npmtakumi-js^2.1.1packages/core/package.json
npmwrite-file-atomic^8.0.0packages/core/package.json
npm@stdout-design/coreworkspace:*packages/dev-server/package.json
npm@vitejs/plugin-react^6.0.3packages/dev-server/package.json
npmchokidar^5.0.0packages/dev-server/package.json
npmhono^4.12.29packages/dev-server/package.json
npmvite^8.1.4packages/dev-server/package.json
npmvite-node^6.0.0packages/dev-server/package.json
npm@base-ui/react^1.6.0packages/web-ui/package.json
npm@fontsource-variable/geist^5.2.9packages/web-ui/package.json
npmclass-variance-authority^0.7.1packages/web-ui/package.json
npmclsx^2.1.1packages/web-ui/package.json
npmlucide-react^1.24.0packages/web-ui/package.json
npmreact^19.2.7packages/web-ui/package.json
npmreact-dom^19.2.7packages/web-ui/package.json
npmshadcn^4.13.0packages/web-ui/package.json
npmtailwind-merge^3.6.0packages/web-ui/package.json
npmtw-animate-css^1.4.0packages/web-ui/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

Dependency advisories 0

Installing npm:@stdout-design/cli@0.3.2 pulls in 35 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

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

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