Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-14 08:43 UTC

TomFrankly / notion-helper

A library of functions for working more easily with the Notion API

JavaScriptMIT★ 97 stars⑂ 6 forkssince Sep 2024View on GitHub ↗

TomFrankly/notion-helper holds a health index of 44 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (60/100) and lowest on Vitality (21/100). It was last updated 38 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Thomas FrankPersonal account
148 followers15 public repossince Mar 2011Thomas Frank

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
npmnotion-helper1.3.3340,35610638 days agonotionnotion-apinotionapibrowserfrontend

Metrics by category

Vitality

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

21At Risk · 21% of overall
How it's scored
18/36Push recency — last push 38 days ago
3.5/36Commit cadence — 5/52 weeks with commits
10/18Commit volume — 12 commits in the last year
2/10OpenSSF Scorecard: Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year12
human_commit_share1
days_since_last_push38
active_weeks_last_year5
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no 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?

53Moderate · 17% of overall
How it's scored
32.2/60Stars — 97 stars
5.8/25Forks — 6 forks
2.7/15Watchers — 4 watchers
Inputs used
forks6
stars97
watchers4
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
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
61.4/80Monthly downloads — 40,356 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesnotion-helper
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads40,356
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?

60Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.2/22.5Commit distribution — top contributor authored 99% of commits
2.7/13.5Contributor breadth — 2 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.992
How it's scored
42/42Issue resolution — 100% of issues closed
30/30PR acceptance — 1/1 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_prs1
open_issues0
closed_issues9
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs0
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
15.6/25Owner reach — 148 followers of TomFrankly
20.8/25Track record — 15 public repos, account ~15 yr old
Inputs used
followers148
owner_typeUser
is_verified—
owner_loginTomFrankly
public_repos15
account_age_days5,684
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 38 days ago
20/20Version history — 106 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesnotion-helper
ecosystemsnpm
any_deprecatedno
min_days_since_publish38

Engineering Quality

Are baseline engineering and documentation practices in place?

48Weak · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
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_ciyes
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.
How it's scored
30/30README
25/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_diryes
has_descriptionyes

Security

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

47Weak · 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.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
1.5/7.5Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
0/5Packaging — no data
0.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
0/7.5Vulnerabilities — 16 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate3.4
Excluded from scoring (no data or not applicable): CI-Tests, 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
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories16
affected_packages5
assessed_packages49
unassessed_packages0
affected_by_severityhigh 3, 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 49 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.

41Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://developers.notion.com/llms.txt)
7.5/40Legible commit history — 14 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://developers.notion.com/llms.txt
legible_history_share0.14
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
1/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — JavaScript with type-check config (tsconfig.json)
44/55Manageable file sizes — 2/10 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes82,305
source_files_sampled10
oversized_source_files2
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
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

97GitHub stars
2contributors
12commits, last 12 months
38days since last push
0releases
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 ★ / 6 ⇿
0Stars
6Forks

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.

123456612024-092025-062026-03

Each point covers 2 days.

OpenSSF Scorecard 3.4 / 10
3.4aggregate

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-10-14 08:42 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
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
2Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
n/aPackagingpackaging workflow not detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
0Vulnerabilities16 existing vulnerabilities detected
All dependencies 49

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

RegistryPackageVersionRelation
npm@esbuild/aix-ppc640.25.9indirect
npm@esbuild/android-arm0.25.9indirect
npm@esbuild/android-arm640.25.9indirect
npm@esbuild/android-x640.25.9indirect
npm@esbuild/darwin-arm640.25.9indirect
npm@esbuild/darwin-x640.25.9indirect
npm@esbuild/freebsd-arm640.25.9indirect
npm@esbuild/freebsd-x640.25.9indirect
npm@esbuild/linux-arm0.25.9indirect
npm@esbuild/linux-arm640.25.9indirect
npm@esbuild/linux-ia320.25.9indirect
npm@esbuild/linux-loong640.25.9indirect
npm@esbuild/linux-mips64el0.25.9indirect
npm@esbuild/linux-ppc640.25.9indirect
npm@esbuild/linux-riscv640.25.9indirect
npm@esbuild/linux-s390x0.25.9indirect
npm@esbuild/linux-x640.25.9indirect
npm@esbuild/netbsd-arm640.25.9indirect
npm@esbuild/netbsd-x640.25.9indirect
npm@esbuild/openbsd-arm640.25.9indirect
npm@esbuild/openbsd-x640.25.9indirect
npm@esbuild/openharmony-arm640.25.9indirect
npm@esbuild/sunos-x640.25.9indirect
npm@esbuild/win32-arm640.25.9indirect
npm@esbuild/win32-ia320.25.9indirect
npm@esbuild/win32-x640.25.9indirect
npm@gerrit0/mini-shiki3.14.0indirect
npm@shikijs/engine-oniguruma3.14.0indirect
npm@shikijs/langs3.14.0indirect
npm@shikijs/themes3.14.0indirect
npm@shikijs/types3.14.0indirect
npm@shikijs/vscode-textmate10.0.2indirect
npm@types/hast3.0.4indirect
npm@types/unist3.0.3indirect
npmargparse2.0.1indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion2.0.2indirect
npmentities4.5.0indirect
npmesbuild0.25.9indirect
npmlinkify-it5.0.0indirect
npmlunr2.3.9indirect
npmmarkdown-it14.1.0indirect
npmmdurl2.0.0indirect
npmminimatch9.0.5indirect
npmpunycode.js2.3.1indirect
npmtypedoc0.28.14indirect
npmtypescript5.9.2indirect
npmuc.micro2.1.0indirect
npmyaml2.8.1indirect
Dependency advisories 5

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

PackageVersionRelationSeverityAdvisoriesFixed in
brace-expansion2.0.2indirecthigh75.0.12
linkify-it5.0.0indirecthigh25.0.2
minimatch9.0.5indirecthigh310.2.3
markdown-it14.1.0indirectmoderate315.0.1
yaml2.8.1indirectmoderate12.8.3

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.