Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-17 16:23 UTC

bartdominiak / vue-snap

🌿 Modern and lightweight Vue 3 Carousel powered by CSS Scroll Snap.

Vue · TypeScriptMIT★ 170 stars⑂ 19 forkssince Jun 2020View on GitHub ↗
KindLibraryWeb interfacehow this is determined

bartdominiak/vue-snap holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Engineering Quality (84/100) and lowest on Security (49/100). It was last updated 2 days ago. 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

Bartosz DominiakPersonal account
12 followers17 public repossince Mar 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmvue-snap2.1.04,477502 days agovuevue-snapcarouselsliderscroll-snap

Metrics by category

Vitality

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

70Good · 21% of overall
How it's scored
36/36Push recencylast push 2 days ago
2.1/36Commit cadence3/52 weeks with commits
12.6/18Commit volume24 commits in the last year
10/10OpenSSF Scorecard: Maintained23 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year24
human_commit_share
days_since_last_push2
active_weeks_last_year3
How it's scored
27/27Ships releases39 releases published
36/36Release recencylatest release 2 days ago
12.6/27Release cadencea release every ~235.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count39
latest_release_tag2.1.0
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases235.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?

53Moderate · 17% of overall
How it's scored
36.1/60Stars170 stars
10.5/25Forks19 forks
3.3/15Watchers5 watchers
Inputs used
forks19
stars170
watchers5
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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
48.7/80Monthly downloads4,477 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesvue-snap
dependents
ecosystemsnpm
total_downloads
monthly_downloads4,477
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?

51Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
2.2/22.5Commit distributiontop contributor authored 90% of commits
8.1/13.5Contributor breadth6 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled6
top_contributor_share0.9
How it's scored
31.2/42Issue resolution74% of issues closed
13.5/30PR acceptance32/71 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs32
open_issues9
closed_issues26
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.743
closed_unmerged_prs39
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.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
8/25Owner reach12 followers of bartdominiak
21.1/25Track record17 public repos, account ~10 yr old
Inputs used
followers12
owner_typeUser
is_verified
owner_loginbartdominiak
public_repos17
account_age_days3,766
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 2 days ago
20/20Version history50 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesvue-snap
ecosystemsnpm
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter configbiome.json
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests10 out of 10 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://vue-snap.vercel.app
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicsvue, carousel, scroll-snapping, vue3
has_wikiyes
homepagehttps://vue-snap.vercel.app
docs_sitehttps://vue-snap.vercel.app
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

49Weak · 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-Tests10 out of 10 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/30 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
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained23 commit(s) and 3 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/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
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.9
Excluded from scoring (no data or not applicable): 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.

71Good · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes1,820
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configbiome.json
11/11Static type checkingexamples/nuxt-app/server/tsconfig.json, examples/nuxt-app/tsconfig.json, tsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configsexamples/nuxt-app/server/tsconfig.json, examples/nuxt-app/tsconfig.json, tsconfig.json
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
27/45Type-checkable codeVue with type-check config (examples/nuxt-app/server/tsconfig.json, examples/nuxt-app/tsconfig.json, tsconfig.json)
55/55Manageable file sizes0/15 source files over 60KB
Inputs used
primary_languageVue
largest_source_bytes4,462
source_files_sampled15
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 examplesdemos, examples
Inputs used
example_dirsdemos, examples
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

170GitHub stars
6contributors
24commits, last 12 months
2days since last push
39releases
1bus factor
9open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 4.9 / 10
4.9aggregate

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

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests10 out of 10 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/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained23 commit(s) and 3 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
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
npmshiki^4.3.1.docs/package.json
npmvue^3.5.39.docs/package.json
npmvue-router^5.1.0.docs/package.json
npmvue-snap^2.0.0.docs/package.json
All dependencies 20

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

RegistryPackageVersionRelation
npmshiki^4.3.1direct
npmvue^3.5.39direct
npmvue-router^5.1.0direct
npmvue-snap^2.0.0direct
npm@biomejs/biome2.5.3indirect
npm@tailwindcss/vite^4.1.0indirect
npm@types/bun^1.3.14indirect
npm@vitejs/plugin-vue^6.0.7indirect
npm@vitejs/plugin-vue^6.0.8indirect
npm@vue/tsconfig^0.9.1indirect
npmnuxt^4.4.8indirect
npmsass-embedded^1.100.0indirect
npmtailwindcss^4.1.0indirect
npmtypescript^6.0.3indirect
npmvite^7.0.0indirect
npmvite^8.1.4indirect
npmvite-plugin-dts^5.0.3indirect
npmvite-plugin-html^3.2.2indirect
npmvite-plugin-vue-devtools^8.1.5indirect
npmvue-tsc^3.3.7indirect
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.12.0 — full methodology · metrics wiki.

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