Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-02 00:04 UTC

JasonPuglisi / e-note-ion

Automation for Vestaboard displays — with emotion

PythonMIT★ 0 stars⑂ 0 forkssince Feb 2026View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

JasonPuglisi/e-note-ion holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (92/100) and lowest on Community & Adoption (47/100). It was last updated today. A single contributor accounts for most of its recent work.

86
overall / 100
Excellent

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.

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

Ownership

Jason PuglisiPersonal account
13 followers20 public repossince Jul 2013@makenotion

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
PyPIe-note-ion2.2.02,261730 days agovestaboardnoteflagshipautomationschedulescheduling

Metrics by category

Vitality

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

86Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
12.5/36Commit cadence — 18/52 weeks with commits
18/18Commit volume — 334 commits in the last year
10/10OpenSSF Scorecard: Maintained — 27 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year334
human_commit_share0.92
days_since_last_push0
active_weeks_last_year18

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~2.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv2.2.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases2.8
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?

47Weak · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
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
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com
has_pull_request_templateyes
How it's scored
44.7/80Monthly downloads — 2,261 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagese-note-ion
dependents—
ecosystemspypi
total_downloads—
monthly_downloads2,261
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
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
39.3/42Issue resolution — 94% of issues closed
28.2/30PR acceptance — 333/354 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/29 approved changesets -- score normalized to 0
Inputs used
merged_prs333
open_issues18
closed_issues257
prs_merged_7d1
prs_decided_7d1
prs_merged_30d24
prs_decided_30d24
issue_closed_ratio0.935
closed_unmerged_prs21
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
8.2/25Owner reach — 13 followers of JasonPuglisi
21.6/25Track record — 20 public repos, account ~13 yr old
Inputs used
followers13
owner_typeUser
is_verified—
owner_loginJasonPuglisi
public_repos20
account_age_days4,816
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 pypi
35/35Publish recency — latest publish 0 days ago
20/20Version history — 73 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagese-note-ion
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

92Excellent · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://github.com/JasonPuglisi/e-note-ion
10/10Repository description
10/10Topics — 7 topics
0/10Wiki
Inputs used
topicscron, docker, home-automation, python, scheduler, split-flap, vestaboard
has_wikino
homepagehttps://github.com/JasonPuglisi/e-note-ion
docs_sitehttps://github.com/JasonPuglisi/e-note-ion
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

81Excellent · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 30 out of 30 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/29 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
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 — 27 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
4.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.6
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 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
advisories0
affected_packages0
assessed_packages72
unassessed_packages0
affected_by_severitynone
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 72 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.

72Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 92 of 92 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes35,532
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 92 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 8 of the last 100 commits are automated dependency updates
9/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.92
toolchain_manifests—
dependency_bot_commit_share0.08
How it's scored
0/45Type-checkable code — Python without a type-check config
53.8/55Manageable file sizes — 2/92 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes113,797
source_files_sampled92
oversized_source_files2

Key facts

0GitHub stars
1contributors
334commits, last 12 months
0days since last push
100releases
1bus factor
18open issues
PyPIpackage ecosystems

Data collection warnings

  • deps.dev does not index pypi:e-note-ion@2.2.0; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 7.6 / 10
7.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-10-02 00:04 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 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/29 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained27 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
9Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
PyPIapscheduler>=3.11.2pyproject.toml
PyPIargon2-cffi>=25.1.0pyproject.toml
PyPIcaldav>=3.2.1pyproject.toml
PyPIicalendar>=7.1.2pyproject.toml
PyPIPillow>=12.3.0pyproject.toml
PyPIrecurring-ical-events>=3.8.2pyproject.toml
PyPIrequests>=2.34.2pyproject.toml
All dependencies 72

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

RegistryPackageVersionRelation
PyPIapscheduler3.11.3direct
PyPIargon2-cffi25.1.0direct
PyPIcaldav3.3.1direct
PyPIicalendar7.3.0direct
PyPIpillow12.3.0direct
PyPIrecurring-ical-events3.8.2direct
PyPIrequests2.34.2direct
PyPIargon2-cffi-bindings26.1.0indirect
PyPIbandit1.9.4indirect
PyPIboolean-py5.0indirect
PyPIcachecontrol0.14.4indirect
PyPIcertifi2026.7.22indirect
PyPIcffi2.1.1indirect
PyPIcfgv3.5.0indirect
PyPIcharset-normalizer3.5.2indirect
PyPIclick8.5.0indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.16.2indirect
PyPIcyclonedx-python-lib11.12.0indirect
PyPIdefusedxml0.7.1indirect
PyPIdistlib0.4.3indirect
PyPIdnspython2.8.0indirect
PyPIe-note-ion2.2.0indirect
PyPIfilelock4.0.9indirect
PyPIh110.16.0indirect
PyPIicalendar-searcher1.0.6indirect
PyPIidentify2.6.20indirect
PyPIidna3.20indirect
PyPIiniconfig2.3.0indirect
PyPIjh25.0.15indirect
PyPIlicense-expression30.4.4indirect
PyPIlxml6.1.3indirect
PyPImarkdown-it-py4.2.0indirect
PyPImdurl0.1.2indirect
PyPImsgpack1.2.3indirect
PyPIniquests3.21.2indirect
PyPInodeenv1.11.0indirect
PyPIpackageurl-python0.17.6indirect
PyPIpackaging26.3indirect
PyPIpip26.2.1indirect
PyPIpip-api0.0.35indirect
PyPIpip-audit2.10.1indirect
PyPIpip-requirements-parser32.0.1indirect
PyPIplatformdirs4.12.2indirect
PyPIpluggy1.6.0indirect
PyPIpre-commit4.6.2indirect
PyPIpy-serializable2.1.0indirect
PyPIpycparser3.0indirect
PyPIpygments2.21.0indirect
PyPIpyparsing3.3.3indirect
PyPIpyright1.1.414indirect
PyPIpytest9.1.1indirect
PyPIpytest-cov7.1.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpython-discovery1.6.1indirect
PyPIpyyaml6.0.3indirect
PyPIqh32.0.4indirect
PyPIrich15.0.0indirect
PyPIruff0.16.10indirect
PyPIsix1.17.0indirect
PyPIsortedcontainers2.4.0indirect
PyPIstevedore5.9.1indirect
PyPItomli2.4.1indirect
PyPItomli-w1.2.0indirect
PyPItyping-extensions4.16.0indirect
PyPItzdata2026.4indirect
PyPItzlocal5.4.4indirect
PyPIurllib32.8.0indirect
PyPIurllib3-future2.25.901indirect
PyPIvirtualenv21.14.3indirect
PyPIwassima2.1.4indirect
PyPIx-wr-timezone2.0.1indirect
Dependency advisories 0

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

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 — PyPI.