Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 05:49 UTC

rootlyhq / rootly-wizard

Guided CLI setup wizard — get your Rootly workspace from empty to incident-ready in minutes

JavaScriptMIT★ 2 stars⑂ 0 forkssince May 2026View on GitHub ↗
KindCommand-line toolLibraryTerminal interfacehow this is determined

rootlyhq/rootly-wizard holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Vitality (73/100) and lowest on Community & Adoption (29/100). It was last updated 36 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

RootlyOrganization · verified domain
46 followers74 public repossince Jan 2021

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@rootly/wizard0.4.11081836 days agorootlyincident-managementon-callclisetupwizard

Metrics by category

Vitality

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

73Good · 21% of overall
How it's scored
18/36Push recency — last push 36 days ago
9/36Commit cadence — 13/52 weeks with commits
18/18Commit volume — 253 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year253
human_commit_share0.95
days_since_last_push36
active_weeks_last_year13

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 17 releases published
36/36Release recency — latest release 36 days ago
27/27Release cadence — a release every ~2.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count17
latest_release_tagv0.4.1
releases_from_tagsno
days_since_latest_release36
mean_days_between_releases2.3
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?

29At Risk · 17% of overall
How it's scored
0/60Stars — 2 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars2
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes
How it's scored
27.2/80Monthly downloads — 108 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@rootly/wizard
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads108
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?

61Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.7/22.5Commit distribution — top contributor authored 97% of commits
2.7/13.5Contributor breadth — 2 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.967
How it's scored
0/42Issue resolution — no issues or no data
23.8/30PR acceptance — 23/29 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/26 approved changesets -- score normalized to 0
Inputs used
merged_prs23
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs6
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
20/20Verified domain
12/25Owner reach — 46 followers of rootlyhq
24.2/25Track record — 74 public repos, account ~5 yr old
Inputs used
followers46
owner_typeOrganization
is_verifiedyes
owner_loginrootlyhq
public_repos74
account_age_days2,052

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 36 days ago
20/20Version history — 18 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@rootly/wizard
ecosystemsnpm
any_deprecatedno
min_days_since_publish36

Engineering Quality

Are baseline engineering and documentation practices in place?

67Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 15 out of 15 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

66Good · 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
2.5/2.5CI-Tests — 15 out of 15 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/26 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 4 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
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 — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.7
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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_packages75
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:@rootly/wizard@0.4.1 runtime dependency closure — what installing the published package pulls in — 75 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.

73Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.rootly.com/llms.txt)
40/40Legible commit history — 86 of 95 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.rootly.com/llms.txt
legible_history_share0.905
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes3,043
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 14 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 5 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.14
toolchain_manifests—
dependency_bot_commit_share0.05
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
53.9/55Manageable file sizes — 1/52 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes83,801
source_files_sampled52
oversized_source_files1

Key facts

2GitHub stars
2contributors
253commits, last 12 months
36days since last push
17releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 5.7 / 10
5.7aggregate

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-13 05:48 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests15 out of 15 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/26 approved changesets -- score normalized to 0
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
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 3
RegistryPackageVersion constraintManifest
npmink^7.0.5package.json
npmkeytar^7.9.0package.json
npmreact^19.2.7package.json
All dependencies 75

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

RegistryPackageVersionRelation
npmink7.1.1direct
npmkeytar7.9.0direct
npmreact19.2.8direct
npm@alcalzone/ansi-tokenize0.3.0indirect
npmansi-escapes7.3.0indirect
npmansi-regex6.2.2indirect
npmansi-styles6.2.3indirect
npmauto-bind5.0.1indirect
npmbase64-js1.5.1indirect
npmbl4.1.0indirect
npmbuffer5.7.1indirect
npmchalk5.6.2indirect
npmchownr1.1.4indirect
npmcli-boxes4.0.1indirect
npmcli-cursor4.0.0indirect
npmcli-truncate6.0.0indirect
npmcode-excerpt4.0.0indirect
npmconvert-to-spaces2.0.1indirect
npmdecompress-response6.0.0indirect
npmdeep-extend0.6.0indirect
npmdetect-libc2.1.2indirect
npmend-of-stream1.4.5indirect
npmenvironment1.1.0indirect
npmes-toolkit1.47.0indirect
npmescape-string-regexp2.0.0indirect
npmexpand-template2.0.3indirect
npmfs-constants1.0.0indirect
npmget-east-asian-width1.6.0indirect
npmgithub-from-package0.0.0indirect
npmieee7541.2.1indirect
npmindent-string5.0.0indirect
npminherits2.0.4indirect
npmini1.3.8indirect
npmis-fullwidth-code-point5.1.0indirect
npmis-in-ci2.0.0indirect
npmmimic-fn2.1.0indirect
npmmimic-response3.1.0indirect
npmminimist1.2.8indirect
npmmkdirp-classic0.5.3indirect
npmnapi-build-utils2.0.0indirect
npmnode-abi3.92.0indirect
npmnode-addon-api4.3.0indirect
npmonce1.4.0indirect
npmonetime5.1.2indirect
npmpatch-console2.0.0indirect
npmprebuild-install7.1.3indirect
npmpump3.0.4indirect
npmrc1.2.8indirect
npmreact-reconciler0.33.0indirect
npmreadable-stream3.6.2indirect
npmrestore-cursor4.0.0indirect
npmsafe-buffer5.2.1indirect
npmscheduler0.27.0indirect
npmsemver7.8.0indirect
npmsignal-exit3.0.7indirect
npmsimple-concat1.0.1indirect
npmsimple-get4.0.1indirect
npmslice-ansi9.0.0indirect
npmstack-utils2.0.6indirect
npmstring-width8.2.1indirect
npmstring_decoder1.3.0indirect
npmstrip-ansi7.2.0indirect
npmstrip-json-comments2.0.1indirect
npmtagged-tag1.0.0indirect
npmtar-fs2.1.4indirect
npmtar-stream2.2.0indirect
npmterminal-size4.0.1indirect
npmtunnel-agent0.6.0indirect
npmtype-fest5.7.0indirect
npmutil-deprecate1.0.2indirect
npmwidest-line6.0.0indirect
npmwrap-ansi10.0.0indirect
npmwrappy1.0.2indirect
npmws8.21.0indirect
npmyoga-layout3.2.1indirect
Dependency advisories 0

Installing npm:@rootly/wizard@0.4.1 pulls in 75 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.