Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-22 22:50 UTC

creatorrr / jaunt

jaunt, dont code.

Python · TypeScriptNo license detected★ 0 stars⑂ 2 forkssince Feb 2026View on GitHub ↗
KindCommand-line toolWeb interfacehow this is determined

creatorrr/jaunt holds a health index of 69 out of 100, placing it in the Good band. It scores highest on AI Readiness (84/100) and lowest on Community & Adoption (27/100). It was last updated 22 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Diwank Singh TomerPersonal account
293 followers219 public repossince Jul 2011@julep-ai

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
PyPIjaunt1.7.1423,4745222 days agoclicode-generationdeveloper-toolsllmtestingtypescript

Metrics by category

Vitality

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

74Good · 21% of overall
How it's scored
28.8/36Push recencylast push 22 days ago
6.9/36Commit cadence10/52 weeks with commits
18/18Commit volume300 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year300
human_commit_share0.82
days_since_last_push22
active_weeks_last_year10
How it's scored
27/27Ships releases43 releases published
36/36Release recencylatest release 22 days ago
27/27Release cadencea release every ~1.7 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count43
latest_release_tagts-v0.1.3
releases_from_tagsno
days_since_latest_release22
mean_days_between_releases1.7

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

27At Risk · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks2 forks
0/15Watchers0 watchers
Inputs used
forks2
stars0
watchers0
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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
58.3/80Monthly downloads23,474 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesjaunt
dependents
ecosystemspypi
total_downloads
monthly_downloads23,474
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?

62Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.8/22.5Commit distributiontop contributor authored 78% of commits
2.7/13.5Contributor breadth2 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.785
How it's scored
42/42Issue resolution100% of issues closed
29.4/30PR acceptance100/102 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs100
open_issues0
closed_issues2
prs_merged_7d0
prs_decided_7d0
prs_merged_30d8
prs_decided_30d9
issue_closed_ratio1
closed_unmerged_prs2
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
17.7/25Owner reach293 followers of creatorrr
25/25Track record219 public repos, account ~15 yr old
Inputs used
followers293
owner_typeUser
is_verified
owner_logincreatorrr
public_repos219
account_age_days5,510
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 pypi
35/35Publish recencylatest publish 22 days ago
20/20Version history52 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesjaunt
ecosystemspypi
any_deprecatedno
min_days_since_publish22

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://creatorrr.github.io/jaunt/
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttps://creatorrr.github.io/jaunt/
docs_sitehttps://creatorrr.github.io/jaunt/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

52Moderate · 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
2.5/2.5CI-Tests22 out of 22 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 6 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
5/5Fuzzingproject is fuzzed
0/2.5Licenselicense file not detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
1.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities50 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate4

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages16
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 pypi:jaunt@1.7.14 runtime dependency closure — what installing the published package pulls in — 16 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.

84Excellent · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md, src/jaunt/__generated__/AGENTS.md, src/jaunt/__generated__/CLAUDE.md
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://creatorrr.github.io/jaunt/llms.txt)
40/40Legible commit history80 of 82 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://creatorrr.github.io/jaunt/llms.txt
legible_history_share0.976
agent_instruction_filesAGENTS.md, CLAUDE.md, src/jaunt/__generated__/AGENTS.md, src/jaunt/__generated__/CLAUDE.md
agent_instruction_max_bytes29,496
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configpyproject.toml ([tool.ruff])
11/11Static type checkingdocs-site/tsconfig.json, examples/typescript-jwt/tsconfig.json, examples/typescript_project_references/packages/app/tsconfig.json, examples/typescript_project_references/packages/core/tsconfig.json, examples/typescript_project_references/tsconfig.json, examples/typescript_slugify/tsconfig.json, packages/jaunt-ts/tsconfig.json, src/jaunt/py.typed, tests/fixtures/typescript_upgrade_1_7_12_pnpm/packages/app/tsconfig.json, tests/fixtures/typescript_upgrade_1_7_12_pnpm/packages/core/tsconfig.json, tests/fixtures/typescript_upgrade_1_7_12_pnpm/tsconfig.json
10/10Reproducible environmentlockfile
10/10Demonstrated agent practice46 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
3/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json, pnpm-lock.yaml, uv.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configsdocs-site/tsconfig.json, examples/typescript-jwt/tsconfig.json, examples/typescript_project_references/packages/app/tsconfig.json, examples/typescript_project_references/packages/core/tsconfig.json, examples/typescript_project_references/tsconfig.json, examples/typescript_slugify/tsconfig.json, packages/jaunt-ts/tsconfig.json, src/jaunt/py.typed, tests/fixtures/typescript_upgrade_1_7_12_pnpm/packages/app/tsconfig.json, tests/fixtures/typescript_upgrade_1_7_12_pnpm/packages/core/tsconfig.json, tests/fixtures/typescript_upgrade_1_7_12_pnpm/tsconfig.json
agent_commit_share0.46
toolchain_manifests
dependency_bot_commit_share0
How it's scored
27/45Type-checkable codePython with type-check config (docs-site/tsconfig.json, examples/typescript-jwt/tsconfig.json, examples/typescript_project_references/packages/app/tsconfig.json, examples/typescript_project_references/packages/core/tsconfig.json, examples/typescript_project_references/tsconfig.json, examples/typescript_slugify/tsconfig.json, packages/jaunt-ts/tsconfig.json, src/jaunt/py.typed, tests/fixtures/typescript_upgrade_1_7_12_pnpm/packages/app/tsconfig.json, tests/fixtures/typescript_upgrade_1_7_12_pnpm/packages/core/tsconfig.json, tests/fixtures/typescript_upgrade_1_7_12_pnpm/tsconfig.json)
53.5/55Manageable file sizes15/547 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes592,443
source_files_sampled547
oversized_source_files15
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
20/20MCP server
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalyes
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

0GitHub stars
2contributors
300commits, last 12 months
22days since last push
43releases
1bus factor
0open issues
npm, PyPIpackage ecosystems

Data collection warnings

  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 2 ⇿
0Stars
2Forks
26Releases

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.

111222212026-072026-072026-07
Major 0Minor 3Patch 14
OpenSSF Scorecard 4.0 / 10
4.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-08-22 22:49 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests22 out of 22 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/30 approved changesets -- score normalized to 0
10Contributorsproject has 6 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
10Fuzzingproject is fuzzed
0Licenselicense file not detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities50 existing vulnerabilities detected
Direct dependencies 16
RegistryPackageVersion constraintManifest
npmfumadocs-core16.5.0docs-site/package.json
npmfumadocs-mdx14.2.6docs-site/package.json
npmfumadocs-ui16.5.0docs-site/package.json
npmlucide-react^0.563.0docs-site/package.json
npmnext16.1.6docs-site/package.json
npmreact^19.2.4docs-site/package.json
npmreact-dom^19.2.4docs-site/package.json
npmtailwind-merge^3.4.0docs-site/package.json
PyPIrich>=13,<15pyproject.toml
PyPIwatchfiles>=1.0.0pyproject.toml
PyPIpytest>=8pyproject.toml
PyPIpytest-asyncio>=1.0pyproject.toml
PyPIanyio>=4.1pyproject.toml
PyPIpyyaml>=6.0pyproject.toml
PyPIhypothesis>=6pyproject.toml
PyPIruff>=0.9pyproject.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Dependency advisories 0

Installing pypi:jaunt@1.7.14 pulls in 16 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 statisticsPyPI.