Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-17 07:31 UTC

sakeenah-wedding / template

Elegant and modern digital wedding invitation template for the Sakeenah platform

JavaScriptCustom license★ 216 stars⑂ 61 forkssince Dec 2024View on GitHub ↗
KindWeb interfacehow this is determined

sakeenah-wedding/template holds a health index of 47 out of 100, placing it in the Weak band. It scores highest on Community & Adoption (68/100) and lowest on Security (26/100). It was last updated 111 days ago. A single contributor accounts for most of its recent work.

47
overall / 100
Weak

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.

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

Ownership

Sakeenah WeddingOrganization
3 followers3 public repossince May 2026

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?

54Moderate · 21% of overall
How it's scored
9.9/36Push recency — last push 111 days ago
6.9/36Commit cadence — 10/52 weeks with commits
18/18Commit volume — 237 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year237
human_commit_share1
days_since_last_push111
active_weeks_last_year10
How it's scored
27/27Ships releases — 3 releases published
27/36Release recency — latest release 111 days ago
19.8/27Release cadence — a release every ~86.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count3
latest_release_tagv2.2.1
releases_from_tagsno
days_since_latest_release111
mean_days_between_releases86.8
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?

68Good · 17% of overall
How it's scored
37.8/60Stars — 216 stars
14.8/25Forks — 61 forks
0/15Watchers — 2 watchers
Inputs used
forks61
stars216
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

86Excellent
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
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_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateyes

Sustainability & Governance

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

34At Risk · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolution — no issues or no data
19.6/30PR acceptance — 15/23 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/7 approved changesets -- score normalized to 0
Inputs used
merged_prs15
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs8
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
4.3/25Owner reach — 3 followers of sakeenah-wedding
5.4/25Track record — 3 public repos, account ~0 yr old
Inputs used
followers3
owner_typeOrganization
is_verifiedno
owner_loginsakeenah-wedding
public_repos3
account_age_days194

Engineering Quality

Are baseline engineering and documentation practices in place?

58Moderate · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — eslint.config.js
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 3 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://invitation.sakeenah.site/
10/10Repository description
10/10Topics — 16 topics
10/10Wiki
Inputs used
topicsislam, islamic, tailwindcss, wedding, wedding-invitation, wedding-template, wedding-website, react, vite, javascript, bun, cloudflare-workers, docker, hono, motion, postgresql
has_wikiyes
homepagehttps://invitation.sakeenah.site/
docs_sitehttps://invitation.sakeenah.site/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

26At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/7 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 5 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate2.6
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. 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.

54Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 88 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.88
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js
11/11Static type checking — jsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesbun.lockb
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsjsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — JavaScript with type-check config (jsconfig.json)
55/55Manageable file sizes — 0/61 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes30,845
source_files_sampled61
oversized_source_files0

Key facts

216GitHub stars
1contributors
237commits, last 12 months
111days since last push
3releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 61 ⇿
0Stars
61Forks
3Releases

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.

01020304050606032024-122025-122026-11
Major 0Minor 2Patch 1

Each point covers 2 days.

OpenSSF Scorecard 2.6 / 10
2.6aggregate

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-11-17 07:31 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/7 approved changesets -- score normalized to 0
10Contributorsproject has 5 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 12
RegistryPackageVersion constraintManifest
npm@hono/node-server^2.0.8package.json
npm@hono/zod-validator^0.8.0package.json
npm@tanstack/react-query^5.101.2package.json
npmmotion^12.42.2package.json
npmhono^4.12.29package.json
npmlucide-react^1.24.0package.json
npmpg^8.22.0package.json
npmreact^19.2.7package.json
npmreact-dom^19.2.7package.json
npmreact-router-dom^7.18.1package.json
npmtw-animate-css^1.4.0package.json
npmzod^4.4.3package.json
All dependencies 30

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

RegistryPackageVersionRelation
npm@hono/node-server^2.0.8direct
npm@hono/zod-validator^0.8.0direct
npm@tanstack/react-query^5.101.2direct
npmhono^4.12.29direct
npmlucide-react^1.24.0direct
npmmotion^12.42.2direct
npmpg^8.22.0direct
npmreact^19.2.7direct
npmreact-dom^19.2.7direct
npmreact-router-dom^7.18.1direct
npmtw-animate-css^1.4.0direct
npmzod^4.4.3direct
npm@cloudflare/workers-types^5.20260712.1indirect
npm@eslint/js^10.0.1indirect
npm@tailwindcss/postcss^4.3.2indirect
npm@types/react^19.2.17indirect
npm@types/react-dom^19.2.3indirect
npm@vitejs/plugin-react^6.0.3indirect
npm@vitest/coverage-v8^4.1.10indirect
npmeslint^10.7.0indirect
npmeslint-plugin-react^7.37.5indirect
npmeslint-plugin-react-hooks^7.1.1indirect
npmeslint-plugin-react-refresh^0.5.3indirect
npmglobals^17.7.0indirect
npmpostcss^8.5.17indirect
npmprettier^3.9.5indirect
npmtailwindcss^4.3.2indirect
npmvite^8.1.4indirect
npmvitest^4.1.10indirect
npmwrangler^4.110.0indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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

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