Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 11:49 UTC

udivankin / sunrise-sunset-js

High-precision sunrise, sunset, twilight, golden-hour & solar-position calculation for JavaScript / TypeScript. Based on NREL's Solar Position Algorithm (SPA). Zero runtime deps, ESM + CommonJS, native Temporal support.

TypeScriptNo license detected★ 97 stars⑂ 18 forkssince Jul 2018View on GitHub ↗

udivankin/sunrise-sunset-js holds a health index of 60 out of 100, placing it in the Moderate band. It scores highest on Vitality (65/100) and lowest on Community & Adoption (44/100). It was last updated 7 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

allxPersonal account
29 followers54 public repossince Mar 2012

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?

65Good · 21% of overall
How it's scored
36/36Push recencylast push 7 days ago
8.3/36Commit cadence12/52 weeks with commits
14.8/18Commit volume43 commits in the last year
6/10OpenSSF Scorecard: Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
Inputs used
commits_last_year43
human_commit_share0.8
days_since_last_push7
active_weeks_last_year12
How it's scored
27/27Ships releases7 releases published
27/36Release recencylatest release 108 days ago
5.4/27Release cadencea release every ~434.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count7
latest_release_tagv3.3.0
releases_from_tagsno
days_since_latest_release108
mean_days_between_releases434.2
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?

44Weak · 17% of overall
How it's scored
32.2/60Stars97 stars
10.3/25Forks18 forks
0/15Watchers1 watchers
Inputs used
forks18
stars97
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
60/80Monthly downloads31,664 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagessunrise-sunset-js
dependents
ecosystemsnpm
total_downloads
monthly_downloads31,664
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?

58Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1.5/22.5Commit distributiontop contributor authored 93% 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.933
How it's scored
42/42Issue resolution100% of issues closed
22.7/30PR acceptance28/37 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/14 approved changesets -- score normalized to 0
Inputs used
merged_prs28
open_issues0
closed_issues12
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs9
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 backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
10.6/25Owner reach29 followers of udivankin
24.7/25Track record54 public repos, account ~14 yr old
Inputs used
followers29
owner_typeUser
is_verified
owner_loginudivankin
public_repos54
account_age_days5,305
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 34 days ago
20/20Version history16 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagessunrise-sunset-js
ecosystemsnpm
any_deprecatedno
min_days_since_publish34

Engineering Quality

Are baseline engineering and documentation practices in place?

59Moderate · 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
0/20OpenSSF Scorecard: CI-Tests0 out of 10 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://udivankin.github.io/sunrise-sunset-js/
10/10Repository description
10/10Topics20 topics
10/10Wiki
Inputs used
topicssunset, sunrise, sunrise-sunset, golden-hour, suncalc, solar, astronomy, blue-hour, dawn, dusk, geolocation, javascript, nodejs, nrel, solar-position, spa, sun, temporal, twilight, typescript
has_wikiyes
homepagehttps://udivankin.github.io/sunrise-sunset-js/
docs_sitehttps://udivankin.github.io/sunrise-sunset-js/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

60Moderate · 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
0/2.5CI-Tests0 out of 10 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 1/14 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
0/2.5Licenselicense file not detected
4.5/7.5Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
5/5Packagingpackaging workflow detected
0.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
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
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
6/7.5Vulnerabilities2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5
Excluded from scoring (no data or not applicable): 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
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories3
affected_packages3
assessed_packages111
unassessed_packages0
affected_by_severityhigh 1, moderate 2
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 111 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

55Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
31.3/40Legible commit history47 of 80 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.588
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingdemo/tsconfig.json, tsconfig.json
10/10Reproducible environmentlockfile
4/10Demonstrated agent practice2 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance20 of the last 100 commits are automated dependency updates
1/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configsdemo/tsconfig.json, tsconfig.json
agent_commit_share0.02
toolchain_manifests
dependency_bot_commit_share0.2
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/28 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes26,581
source_files_sampled28
oversized_source_files0

Key facts

97GitHub stars
6contributors
43commits, last 12 months
7days since last push
7releases
1bus factor
0open 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 ★ / 18 ⇿
0Stars
18Forks
7Releases

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.

0481216201822019-032022-112026-07
Major 1Minor 3Patch 3

Each point covers 7 days.

OpenSSF Scorecard 5.0 / 10
5.0aggregate

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-18 11:49 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 10 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 1/14 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
0Licenselicense file not detected
6Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
10Packagingpackaging workflow detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
8Vulnerabilities2 existing vulnerabilities detected
All dependencies 111

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

RegistryPackageVersionRelation
npm@babel/helper-string-parser7.29.7indirect
npm@babel/helper-validator-identifier7.29.7indirect
npm@babel/parser7.29.7indirect
npm@babel/types7.29.7indirect
npm@bcoe/v8-coverage1.0.2indirect
npm@dimforge/rapier3d-compat0.12.0indirect
npm@emnapi/core1.10.0indirect
npm@emnapi/runtime1.10.0indirect
npm@emnapi/wasi-threads1.2.1indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/sourcemap-codec1.5.5indirect
npm@jridgewell/trace-mapping0.3.31indirect
npm@napi-rs/wasm-runtime1.1.4indirect
npm@napi-rs/wasm-runtime1.1.5indirect
npm@oxc-project/types0.133.0indirect
npm@rolldown/binding-android-arm641.0.3indirect
npm@rolldown/binding-darwin-arm641.0.3indirect
npm@rolldown/binding-darwin-x641.0.3indirect
npm@rolldown/binding-freebsd-x641.0.3indirect
npm@rolldown/binding-linux-arm-gnueabihf1.0.3indirect
npm@rolldown/binding-linux-arm64-gnu1.0.3indirect
npm@rolldown/binding-linux-arm64-musl1.0.3indirect
npm@rolldown/binding-linux-ppc64-gnu1.0.3indirect
npm@rolldown/binding-linux-s390x-gnu1.0.3indirect
npm@rolldown/binding-linux-x64-gnu1.0.3indirect
npm@rolldown/binding-linux-x64-musl1.0.3indirect
npm@rolldown/binding-openharmony-arm641.0.3indirect
npm@rolldown/binding-wasm32-wasi1.0.3indirect
npm@rolldown/binding-win32-arm64-msvc1.0.3indirect
npm@rolldown/binding-win32-x64-msvc1.0.3indirect
npm@rolldown/pluginutils1.0.1indirect
npm@standard-schema/spec1.1.0indirect
npm@tweenjs/tween.js23.1.3indirect
npm@tybys/wasm-util0.10.2indirect
npm@types/chai5.2.3indirect
npm@types/deep-eql4.0.2indirect
npm@types/estree1.0.9indirect
npm@types/node24.10.2indirect
npm@types/stats.js0.17.4indirect
npm@types/three0.180.0indirect
npm@types/webxr0.5.24indirect
npm@vitest/coverage-v84.1.8indirect
npm@vitest/expect4.1.8indirect
npm@vitest/mocker4.1.8indirect
npm@vitest/pretty-format4.1.8indirect
npm@vitest/runner4.1.8indirect
npm@vitest/snapshot4.1.8indirect
npm@vitest/spy4.1.8indirect
npm@vitest/utils4.1.8indirect
npm@webgpu/types0.1.70indirect
npmassertion-error2.0.1indirect
npmast-v8-to-istanbul1.0.3indirect
npmchai6.2.2indirect
npmconvert-source-map2.0.0indirect
npmdetect-libc2.1.2indirect
npmes-module-lexer2.1.0indirect
npmestree-walker3.0.3indirect
npmexpect-type1.3.0indirect
npmfdir6.5.0indirect
npmfflate0.8.3indirect
npmfsevents2.3.3indirect
npmgsap3.15.0indirect
npmhas-flag4.0.0indirect
npmhtml-escaper2.0.2indirect
npmistanbul-lib-coverage3.2.2indirect
npmistanbul-lib-report3.0.1indirect
npmistanbul-reports3.2.0indirect
npmjs-tokens10.0.0indirect
npmlightningcss1.32.0indirect
npmlightningcss-android-arm641.32.0indirect
npmlightningcss-darwin-arm641.32.0indirect
npmlightningcss-darwin-x641.32.0indirect
npmlightningcss-freebsd-x641.32.0indirect
npmlightningcss-linux-arm-gnueabihf1.32.0indirect
npmlightningcss-linux-arm64-gnu1.32.0indirect
npmlightningcss-linux-arm64-musl1.32.0indirect
npmlightningcss-linux-x64-gnu1.32.0indirect
npmlightningcss-linux-x64-musl1.32.0indirect
npmlightningcss-win32-arm64-msvc1.32.0indirect
npmlightningcss-win32-x64-msvc1.32.0indirect
npmmagic-string0.30.21indirect
npmmagicast0.5.3indirect
npmmake-dir4.0.0indirect
npmmeshoptimizer0.22.0indirect
npmnanoid3.3.16indirect
npmnanoid3.3.18indirect
npmobug2.1.1indirect
npmpathe2.0.3indirect
npmpicocolors1.1.1indirect
npmpicomatch4.0.4indirect
npmpostcss8.5.25indirect
npmpostcss8.5.26indirect
npmrolldown1.0.3indirect
npmsemver7.7.3indirect
npmsiginfo2.0.0indirect
npmsource-map-js1.2.1indirect
npmstackback0.0.2indirect
npmstd-env4.1.0indirect
npmsupports-color7.2.0indirect
npmthree0.180.0indirect
npmtinybench2.9.0indirect
npmtinyexec1.2.4indirect
npmtinyglobby0.2.17indirect
npmtinyrainbow3.1.0indirect
npmtslib2.8.1indirect
npmtypescript5.9.3indirect
npmtz-lookup6.1.25indirect
npmundici-types7.16.0indirect
npmvite8.0.16indirect
npmvitest4.1.8indirect
npmwhy-is-node-running2.3.0indirect
Dependency advisories 3

This repository publishes no package the index resolves, so its own dependency graph was assessed — 111 packages, which also include development and test pins that never ship: 3 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
nanoid3.3.16indirecthigh15.1.6
@vitest/mocker4.1.8indirectmoderate15.0.0-rc.2
vitest4.1.8indirectmoderate15.0.0-rc.2

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