Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 02:25 UTC

vkurko / calendar

Full-sized drag & drop JavaScript event calendar with resource & timeline views

JavaScript · SvelteMIT★ 2,277 stars⑂ 199 forkssince Jul 2020View on GitHub ↗
KindLibraryWeb interfacehow this is determined

vkurko/calendar holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Community & Adoption (85/100) and lowest on AI Readiness (22/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

VladimirPersonal account
55 followers3 public repossince Sep 2011

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
npm@event-calendar/core5.12.3196,9711652 days agocalendareventresourcetimelinefull-sized
npm@event-calendar/build5.12.33,0231652 days agocalendareventresourcetimelinefull-sized

Metrics by category

Vitality

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

82Excellent · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
16.6/36Commit cadence — 24/52 weeks with commits
14.8/18Commit volume — 44 commits in the last year
10/10OpenSSF Scorecard: Maintained — 11 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year44
human_commit_share1
days_since_last_push2
active_weeks_last_year24
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 2 days ago
27/27Release cadence — a release every ~7.7 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv5.12.3
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases7.7

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

85Excellent · 17% of overall
How it's scored
54.5/60Stars — 2,277 stars
19.1/25Forks — 199 forks
8.1/15Watchers — 30 watchers
Inputs used
forks199
stars2,277
watchers30
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
70.7/80Monthly downloads — 199,994 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@event-calendar/core, @event-calendar/build
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads199,994
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?

56Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
2.3/22.5Commit distribution — top contributor authored 90% of commits
13.5/13.5Contributor breadth — 19 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled19
top_contributor_share0.897
How it's scored
39.6/42Issue resolution — 94% of issues closed
16.8/30PR acceptance — 19/34 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs19
open_issues25
closed_issues416
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.943
closed_unmerged_prs15
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
12.6/25Owner reach — 55 followers of vkurko
16.4/25Track record — 3 public repos, account ~14 yr old
Inputs used
followers55
owner_typeUser
is_verified—
owner_loginvkurko
public_repos3
account_age_days5,467
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 2 package(s) on npm
35/35Publish recency — latest publish 2 days ago
20/20Version history — 165 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@event-calendar/core, @event-calendar/build
ecosystemsnpm
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

37Weak · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
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.

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://vkurko.github.io/calendar/
10/10Repository description
10/10Topics — 4 topics
0/10Wiki
Inputs used
topicscalendar, event, full-sized, resource
has_wikino
homepagehttps://vkurko.github.io/calendar/
docs_sitehttps://vkurko.github.io/calendar/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

46Weak · 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 — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 11 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate3.3
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages19
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:@event-calendar/core@5.12.3 runtime dependency closure — what installing the published package pulls in — 19 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.

22At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
19.7/40Legible commit history — 37 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.37
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — 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 — no data
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/55 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes15,408
source_files_sampled55
oversized_source_files0

Key facts

2,277GitHub stars
19contributors
44commits, last 12 months
2days since last push
100releases
1bus factor
25open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 199 ⇿
0Stars
199Forks
97Releases

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.

0408012016020019952021-102024-032026-08
Major 4Minor 40Patch 53

Each point covers 5 days.

OpenSSF Scorecard 3.3 / 10
3.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-09-12 02:24 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/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
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained11 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
npmsvelte^5.57.0packages/core/package.json
All dependencies 66

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

RegistryPackageVersionRelation
npmsvelte5.57.0direct
npmsvelte^5.57.0direct
npm@jridgewell/gen-mapping0.3.13indirect
npm@jridgewell/remapping2.3.5indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/sourcemap-codec1.5.5indirect
npm@jridgewell/trace-mapping0.3.31indirect
npm@oxc-project/types0.147.0indirect
npm@rolldown/binding-android-arm-eabi1.2.6indirect
npm@rolldown/binding-android-arm641.2.6indirect
npm@rolldown/binding-darwin-arm641.2.6indirect
npm@rolldown/binding-darwin-x641.2.6indirect
npm@rolldown/binding-freebsd-x641.2.6indirect
npm@rolldown/binding-linux-arm-gnueabihf1.2.6indirect
npm@rolldown/binding-linux-arm64-gnu1.2.6indirect
npm@rolldown/binding-linux-arm64-musl1.2.6indirect
npm@rolldown/binding-linux-ppc64-gnu1.2.6indirect
npm@rolldown/binding-linux-s390x-gnu1.2.6indirect
npm@rolldown/binding-linux-x64-gnu1.2.6indirect
npm@rolldown/binding-linux-x64-musl1.2.6indirect
npm@rolldown/binding-openharmony-arm641.2.6indirect
npm@rolldown/binding-win32-arm64-msvc1.2.6indirect
npm@rolldown/binding-win32-x64-msvc1.2.6indirect
npm@rolldown/pluginutils1.0.1indirect
npm@sveltejs/acorn-typescript1.0.10indirect
npm@sveltejs/vite-plugin-svelte7.3.0indirect
npm@types/estree1.0.8indirect
npmacorn8.16.0indirect
npmaria-query5.3.1indirect
npmaxobject-query4.1.0indirect
npmclsx2.1.1indirect
npmdeepmerge4.3.1indirect
npmdetect-libc2.1.2indirect
npmdevalue5.8.1indirect
npmesm-env1.2.2indirect
npmesrap2.2.13indirect
npmfdir6.5.0indirect
npmfsevents2.3.3indirect
npmis-reference3.0.3indirect
npmlightningcss1.33.0indirect
npmlightningcss-android-arm641.33.0indirect
npmlightningcss-darwin-arm641.33.0indirect
npmlightningcss-darwin-x641.33.0indirect
npmlightningcss-freebsd-x641.33.0indirect
npmlightningcss-linux-arm-gnueabihf1.33.0indirect
npmlightningcss-linux-arm64-gnu1.33.0indirect
npmlightningcss-linux-arm64-musl1.33.0indirect
npmlightningcss-linux-x64-gnu1.33.0indirect
npmlightningcss-linux-x64-musl1.33.0indirect
npmlightningcss-win32-arm64-msvc1.33.0indirect
npmlightningcss-win32-x64-msvc1.33.0indirect
npmlocate-character3.0.0indirect
npmmagic-string0.30.21indirect
npmmagic-string1.2.3indirect
npmnanoid3.3.18indirect
npmobug2.1.1indirect
npmpicocolors1.1.1indirect
npmpicomatch4.0.5indirect
npmpostcss8.5.26indirect
npmrolldown1.2.6indirect
npmsource-map-js1.2.1indirect
npmtinyglobby0.2.17indirect
npmvite8.2.2indirect
npmvite-plugin-banner0.8.1indirect
npmvitefu1.1.2indirect
npmzimmerframe1.1.4indirect
Dependency advisories 0

Installing npm:@event-calendar/core@5.12.3 pulls in 19 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.34.0 — full methodology · metrics wiki.

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