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

kiln / flourish-sdk

The SDK for developing Flourish templates

JavaScriptCustom license★ 87 stars⑂ 18 forkssince Mar 2017View on GitHub ↗
KindLibraryCommand-line toolNetwork servicehow this is determined

kiln/flourish-sdk holds a health index of 36 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (56/100) and lowest on Vitality (18/100). It was last updated 38 days ago. A single contributor accounts for most of its recent work.

36
overall / 100
Weak

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.

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

Ownership

KilnOrganization
35 followers66 public repossince Feb 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npm@flourish/sdk5.2.103,49110938 days ago
npmuntitled_flourish_templatepoints to another repo — not scored0.0.1-security101487 days ago

Metrics by category

Vitality

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

18Critical · 21% of overall
How it's scored
18/36Push recencylast push 38 days ago
4.2/36Commit cadence6/52 weeks with commits
7.6/18Commit volume6 commits in the last year
0/10OpenSSF Scorecard: Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year6
human_commit_share1
days_since_last_push38
active_weeks_last_year6
How it's scored
0/27Ships releasesno releases published
0/36Release recencyno releases
0/27Release cadenceno releases
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count0
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?

49Weak · 17% of overall
How it's scored
31.4/60Stars87 stars
10.3/25Forks18 forks
6.5/15Watchers16 watchers
Inputs used
forks18
stars87
watchers16
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/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_templateno
How it's scored
47.2/80Monthly downloads3,491 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@flourish/sdk
dependents
ecosystemsnpm
total_downloads
monthly_downloads3,491
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 factor1 contributor(s) cover half of all commits
9.1/22.5Commit distributiontop contributor authored 60% of commits
13.5/13.5Contributor breadth15 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled15
top_contributor_share0.597
How it's scored
23.7/42Issue resolution56% of issues closed
7.5/30PR acceptance1/4 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/29 approved changesets -- score normalized to 0
Inputs used
merged_prs1
open_issues41
closed_issues53
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.564
closed_unmerged_prs3
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
30/30Ownership backingorganization-owned
0/20Verified domain
11.2/25Owner reach35 followers of kiln
25/25Track record66 public repos, account ~14 yr old
Inputs used
followers35
owner_typeOrganization
is_verifiedno
owner_loginkiln
public_repos66
account_age_days5,317

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 38 days ago
20/20Version history109 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@flourish/sdk
ecosystemsnpm
any_deprecatedno
min_days_since_publish38

Engineering Quality

Are baseline engineering and documentation practices in place?

44Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config.eslintrc.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 1 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

36Weak · 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 1 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/29 approved changesets -- score normalized to 0
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
0/7.5Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesno data
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-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2.6
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
8.8/25Indirect dependencies free of known advisories1 affected: serialize-javascript 6.0.2 (high 8.1)
33.3/40No advisories left outstanding1 advisory-carrying package(s) unaddressed past 90 days; oldest published 202 days ago
Inputs used
sourceosv
advisories2
affected_packages1
assessed_packages250
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages0
Matched the npm:@flourish/sdk@5.2.10 runtime dependency closure — what installing the published package pulls in — 250 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.

40Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
3.1/40Legible commit history4 of 68 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.059
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc.json
11/11Static type checkingtsconfig.json
0/10Reproducible environment
2.9/10Demonstrated agent practice1 of the last 68 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0.015
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
27/45Type-checkable codeJavaScript with type-check config (tsconfig.json)
54.1/55Manageable file sizes1/61 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes297,067
source_files_sampled61
oversized_source_files1

Key facts

87GitHub stars
15contributors
6commits, last 12 months
38days since last push
0releases
1bus factor
41open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package '@flourish/common' from its registry
  • npm package 'untitled_flourish_template' points at a different repository (npm/security-holder); excluded from ecosystem scoring

More detail

Star and fork history 0 ★ / 18 ⇿
0Stars
18Forks

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.

0481216201722017-032021-092026-02

Each point covers 9 days.

OpenSSF Scorecard 2.6 / 10
2.6aggregate

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 18:48 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 1 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/29 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
0Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 33
RegistryPackageVersion constraintManifest
npm@adobe/css-tools^4.3.3common/package.json
npm@flourish/interpreter^9.2.0common/package.json
npmdompurify^3.2.4common/package.json
npm@flourish/interpreter^9.2.0package.json
npm@flourish/semver^1.0.2package.json
npm@flourish/transform-data^2.1.0package.json
npm@handlebars/allow-prototype-access^1.0.5package.json
npm@rollup/plugin-commonjs^25.0.7package.json
npm@rollup/plugin-terser^0.4.4package.json
npmarchiver^7.0.1package.json
npmc8^10.1.3package.json
npmchokidar^4.0.3package.json
npmcross-spawn^7.0.3package.json
npmd3-dsv^2.0.0package.json
npmexpress^4.19.2package.json
npmhandlebars^4.7.8package.json
npmjs-yaml^4.1.0package.json
npmminimist^1.2.8package.json
npmncp^2.0.0package.json
npmnode-fetch^3.3.2package.json
npmparse5^7.1.2package.json
npmpicocolors^1.0.1package.json
npmread^3.0.1package.json
npmresolve^1.22.8package.json
npmrewrite-links^1.1.0package.json
npmshell-quote^1.8.1package.json
npmtmp^0.2.3package.json
npmws^8.17.0package.json
npmless^3.0.1skeleton/package.json
npmless-plugin-clean-css^1.5.1skeleton/package.json
npmrollup^1.16.2skeleton/package.json
npmrollup-plugin-node-resolve^5.1.0skeleton/package.json
npmrollup-plugin-uglify^6.0.2skeleton/package.json
All dependencies 53

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

RegistryPackageVersionRelation
npm@adobe/css-tools^4.3.3direct
npm@flourish/interpreter^9.2.0direct
npm@flourish/semver^1.0.2direct
npm@flourish/transform-data^2.1.0direct
npm@handlebars/allow-prototype-access^1.0.5direct
npm@rollup/plugin-commonjs^25.0.7direct
npm@rollup/plugin-terser^0.4.4direct
npmarchiver^7.0.1direct
npmc8^10.1.3direct
npmchokidar^4.0.3direct
npmcross-spawn^7.0.3direct
npmd3-dsv^2.0.0direct
npmdompurify^3.2.4direct
npmexpress^4.19.2direct
npmhandlebars^4.7.8direct
npmjs-yaml^4.1.0direct
npmless^3.0.1direct
npmless-plugin-clean-css^1.5.1direct
npmminimist^1.2.8direct
npmncp^2.0.0direct
npmnode-fetch^3.3.2direct
npmparse5^7.1.2direct
npmpicocolors^1.0.1direct
npmread^3.0.1direct
npmresolve^1.22.8direct
npmrewrite-links^1.1.0direct
npmrollup^1.16.2direct
npmrollup^4.17.2direct
npmrollup-plugin-node-resolve^5.1.0direct
npmrollup-plugin-uglify^6.0.2direct
npmshell-quote^1.8.1direct
npmtmp^0.2.3direct
npmws^8.17.0direct
npm@rollup/plugin-alias^6.0.0indirect
npm@rollup/plugin-node-resolve^15.2.3indirect
npm@rollup/plugin-replace^6.0.3indirect
npm@types/jest^29.5.12indirect
npmd3-request^1.0.6indirect
npmjest^29.7.0indirect
npmjest-junit^16.0.0indirect
npmmobx^6.13.5indirect
npmmobx-react-lite^4.1.1indirect
npmmocha^10.4.0indirect
npmmocha-junit-reporter^2.2.1indirect
npmmocha-multi-reporters^1.5.1indirect
npmreact^19.2.1indirect
npmreact-dom^19.2.1indirect
npmrollup-plugin-postcss^4.0.2indirect
npmrollup-plugin-typescript2^0.36.0indirect
npmsass^1.77.0indirect
npmsinon^18.0.0indirect
npmtempy^3.1.0indirect
npmts-jest^29.1.5indirect
Dependency advisories 1

Installing npm:@flourish/sdk@5.2.10 pulls in 250 packages, direct and transitive: 1 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
serialize-javascript6.0.2indirecthigh27.0.5

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.