schmooky / open-slot-ui
schmooky/open-slot-ui holds a health index of 9 out of 100, placing it in the Critical band. It scores highest on Vitality (65/100) and lowest on Security (4/100). It was last updated 12 days ago. A single contributor accounts for most of its recent work.
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.
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). High-Risk Jurisdiction Policy applies a 20% multiplier to weighted overall health and gives it an At Risk ceiling of 34.
Ownership
This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish | Tags |
|---|---|---|---|---|---|---|
| npm | @open-slot-ui/core | 0.13.4 | 3,710 | 35 | 12 days ago | slotslotsigamingcasinogame-uihudheadlessstate-machinepixijstypescript |
| npm | @open-slot-ui/pixi | 0.13.4 | 3,098 | 35 | 12 days ago | pixijspixislotslotsigamingcasinogame-uihudwebgltypescript |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
Development activity
How it's scored
| 28.8/36 | Push recency — last push 12 days ago |
| 3.5/36 | Commit cadence — 5/52 weeks with commits |
| 18/18 | Commit volume — 99 commits in the last year |
| 0/10 | OpenSSF Scorecard: Maintained — project was created within the last 90 days. Please review its contents carefully |
Inputs used
| commits_last_year | 99 |
| human_commit_share | 1 |
| days_since_last_push | 12 |
| active_weeks_last_year | 5 |
Release discipline
How it's scored
| 16.2/27 | Ships releases — 27 version tags (no GitHub releases) |
| 36/36 | Release recency — latest release 14 days ago |
| 27/27 | Release cadence — a release every ~1.7 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 27 |
| latest_release_tag | v0.11.1 |
| releases_from_tags | yes |
| days_since_latest_release | 14 |
| mean_days_between_releases | 1.7 |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
Popularity & adoption
How it's scored
| 0/60 | Stars — 2 stars |
| 0/25 | Forks — 0 forks |
| 0/15 | Watchers — 0 watchers |
Inputs used
| forks | 0 |
| stars | 2 |
| watchers | 0 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (MIT) |
| 18/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 | 4 |
| has_contributing | yes |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | github.com, shields.io |
| has_pull_request_template | no |
Ecosystem adoption (downloads)
How it's scored
| 51.1/80 | Monthly downloads — 6,808 downloads/month across npm |
| 0/20 | Registry dependents — not reported by this ecosystem |
Inputs used
| packages | @open-slot-ui/core, @open-slot-ui/pixi |
| dependents | — |
| ecosystems | npm |
| total_downloads | — |
| monthly_downloads | 6,808 |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
Maintainer resilience (bus factor)
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 0.5/22.5 | Commit distribution — top contributor authored 98% of commits |
| 4.1/13.5 | Contributor breadth — 3 contributors |
| 0/10 | OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0 |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 3 |
| top_contributor_share | 0.98 |
Issue & PR responsiveness
How it's scored
| 0/42 | Issue resolution — no issues or no data |
| 28.6/30 | PR acceptance — 20/21 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 | 20 |
| open_issues | 0 |
| closed_issues | 0 |
| prs_merged_7d | 0 |
| prs_decided_7d | 0 |
| prs_merged_30d | 0 |
| prs_decided_30d | 0 |
| issue_closed_ratio | — |
| closed_unmerged_prs | 1 |
| first_time_authors_30d | 0 |
| first_time_prs_merged_30d | 0 |
| first_time_prs_decided_30d | 0 |
Ownership & stewardship
How it's scored
| 10/30 | Ownership backing — personal (user) account |
| 0/20 | Verified domain — not applicable to user accounts |
| 10.2/25 | Owner reach — 25 followers of schmooky |
| 24.3/25 | Track record — 48 public repos, account ~8 yr old |
Inputs used
| followers | 25 |
| owner_type | User |
| is_verified | — |
| owner_login | schmooky |
| public_repos | 48 |
| account_age_days | 3,001 |
Package maintenance
How it's scored
| 25/25 | Published & resolvable — 2 package(s) on npm |
| 35/35 | Publish recency — latest publish 12 days ago |
| 20/20 | Version history — 35 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | @open-slot-ui/core, @open-slot-ui/pixi |
| ecosystems | npm |
| any_deprecated | no |
| min_days_since_publish | 12 |
Engineering Quality
Are baseline engineering and documentation practices in place?
Engineering practices
How it's scored
| 24/24 | CI workflows — 2 workflow(s) |
| 24/24 | Tests present |
| 0/16 | Linter config |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 0/20 | OpenSSF Scorecard: CI-Tests — no data |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | no |
| has_precommit_config | no |
Documentation
How it's scored
| 30/30 | README |
| 25/25 | Documentation directory |
| 0/15 | Documentation / homepage site |
| 0/10 | Repository description |
| 0/10 | Topics |
| 10/10 | Wiki |
Inputs used
| topics | — |
| has_wiki | yes |
| homepage | — |
| has_readme | yes |
| has_docs_dir | yes |
| has_description | no |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
Security posture
High-risk jurisdiction exposure detected
Based on self-published public profile locations. This governance signal does not determine nationality, citizenship, intent, sanctions status, or individual trustworthiness.
How jurisdiction exposure is assessedHow 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 |
| 0/2.5 | Contributors — project has 0 contributing companies or organizations -- score normalized to 0 |
| 10/10 | Dangerous-Workflow — no dangerous workflow patterns detected |
| 0/7.5 | Dependency-Update-Tool — no update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 0/7.5 | Maintained — project was created within the last 90 days. Please review its contents carefully |
| 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 |
| 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 — 10 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 15 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 3 |
| scorecard_aggregate | 2.2 |
| high_risk_jurisdiction_cap | 34 |
| high_risk_jurisdiction_multiplier | 20 |
| security_posture_after_multiplier | 4 |
| security_posture_before_jurisdiction | 22 |
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.
Agent context & guidance
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 40/40 | Legible commit history — 96 of 99 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | no |
| legible_history_share | 0.97 |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
Verify loop (build / test / typecheck)
How it's scored
| 0/18 | One-command bootstrap |
| 22/22 | Automated tests |
| 0/11 | Lint / format config |
| 11/11 | Static type checking — apps/site/tsconfig.json, examples/demo/tsconfig.json, packages/core/tsconfig.json, packages/pixi-text-counter/tsconfig.json, packages/pixi/tsconfig.json |
| 10/10 | Reproducible environment — lockfile |
| 10/10 | Demonstrated agent practice — 72 of the last 99 commits agent-authored or agent-credited |
| 0/8 | Automated maintenance — no automated dependency updates observed |
| 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 | pnpm-lock.yaml |
| has_dockerfile | no |
| typed_language | yes |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | no |
| typecheck_configs | apps/site/tsconfig.json, examples/demo/tsconfig.json, packages/core/tsconfig.json, packages/pixi-text-counter/tsconfig.json, packages/pixi/tsconfig.json |
| agent_commit_share | 0.727 |
| toolchain_manifests | — |
| dependency_bot_commit_share | 0 |
Code legibility for models
How it's scored
| 45/45 | Type-checkable code — TypeScript (statically typed) |
| 55/55 | Manageable file sizes — 0/146 source files over 60KB |
Inputs used
| primary_language | TypeScript |
| largest_source_bytes | 38,668 |
| source_files_sampled | 146 |
| oversized_source_files | 0 |
How it's scored
| 0/40 | API schema (OpenAPI/GraphQL/proto) |
| 0/20 | MCP server |
| 40/40 | Runnable examples — examples, recipes |
Inputs used
| example_dirs | examples, recipes |
| has_mcp_signal | no |
| api_schema_files | — |
Key facts
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.2 / 10
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).
| 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 |
| 0 | Contributors | project has 0 contributing companies or organizations -- score normalized to 0 |
| 10 | Dangerous-Workflow | no dangerous workflow patterns detected |
| 0 | Dependency-Update-Tool | no update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 0 | Maintained | project was created within the last 90 days. Please review its contents carefully |
| 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 |
| 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 | 10 existing vulnerabilities detected |
Direct dependencies 6
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| npm | @astrojs/mdx | ^5.0.3 | apps/site/package.json |
| npm | @tailwindcss/vite | ^4.2.2 | apps/site/package.json |
| npm | astro | ^6.1.8 | apps/site/package.json |
| npm | tailwindcss | ^4.2.2 | apps/site/package.json |
| npm | tailwindcss-animate | ^1.0.7 | apps/site/package.json |
| npm | @open-slot-ui/core | workspace:* | packages/pixi/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
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.31.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics — npm.