Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-23 04:44 UTC

Nuosis / tau-by-clarity

Python port of pi-mono: fully-aligned coding agent with TUI, ai, agent, and coding-agent packages

PythonNo license detected★ 0 stars⑂ 0 forkssince Jun 2026forkView on GitHub ↗
KindCommand-line toolLibraryTerminal interfacehow this is determined

Nuosis/tau-by-clarity holds a health index of 36 out of 100, placing it in the Weak band. It scores highest on Vitality (74/100) and lowest on Community & Adoption (14/100). It was last updated today. 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

Marcus SwiftPersonal account
4 followers83 public repossince Jan 2023Clarity Custom Software

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
PyPItau-by-clarity0.56.352,071540 days agoagentaianthropicclicoding-agentllmopenaitui

Metrics by category

Vitality

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

74Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
9.7/36Commit cadence14/52 weeks with commits
18/18Commit volume196 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year196
human_commit_share1
days_since_last_push0
active_weeks_last_year14
How it's scored
16.2/27Ships releases12 version tags (no GitHub releases)
36/36Release recencylatest release 71 days ago
27/27Release cadencea release every ~0 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count12
latest_release_tagv0.54.11
releases_from_tagsyes
days_since_latest_release71
mean_days_between_releases0
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?

14Critical · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/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_readmeno
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
44.2/80Monthly downloads2,071 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagestau-by-clarity
dependents
ecosystemspypi
total_downloads
monthly_downloads2,071
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?

46Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.7/22.5Commit distributiontop contributor authored 97% of commits
2.7/13.5Contributor breadth2 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.97
How it's scored
0/42Issue resolution0% of issues closed
30/30PR acceptance2/2 decided PRs merged
13/13Newcomer PR acceptance2/2 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/25 approved changesets -- score normalized to 0
Inputs used
merged_prs2
open_issues3
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0
closed_unmerged_prs0
first_time_authors_30d1
first_time_prs_merged_30d2
first_time_prs_decided_30d2
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
5/25Owner reach4 followers of Nuosis
20.1/25Track record83 public repos, account ~3 yr old
Inputs used
followers4
owner_typeUser
is_verified
owner_loginNuosis
public_repos83
account_age_days1,301
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 0 days ago
20/20Version history54 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagestau-by-clarity
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

38Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter configpyproject.toml ([tool.ruff])
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 2 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
How it's scored
0/30README
25/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_site
has_readmeno
has_docs_diryes
has_descriptionno

Security

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

21At Risk · 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 2 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 0/25 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
0/2.5Licenselicense file not detected
0/7.5Maintainedproject was created within the last 90 days. Please review its contents carefully
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate2.1
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. Remaining weights renormalized.

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.

52Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
25.6/40Legible commit history48 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.48
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configpyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environmentDockerfile, lockfile
10/10Demonstrated agent practice7 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.07
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codePython without a type-check config
53.1/55Manageable file sizes11/321 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes305,528
source_files_sampled321
oversized_source_files11
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
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

0GitHub stars
2contributors
196commits, last 12 months
0days since last push
12releases
1bus factor
3open issues
PyPIpackage ecosystems

Data collection warnings

  • Community profile unavailable
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • deps.dev does not index pypi:tau-by-clarity@0.56.35; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 2.1 / 10
2.1aggregate

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-23 04:44 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 2 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 0/25 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
0Licenselicense file not detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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 18
RegistryPackageVersion constraintManifest
PyPIpydantic>=2.0.0pyproject.toml
PyPIanthropic>=0.40.0pyproject.toml
PyPIopenai>=1.50.0pyproject.toml
PyPIgoogle-genai>=1.64.0pyproject.toml
PyPIboto3>=1.35.0pyproject.toml
PyPIhttpx>=0.27.0pyproject.toml
PyPIaiohttp>=3.9.0pyproject.toml
PyPIjsonschema>=4.0.0pyproject.toml
PyPItyper>=0.12.0pyproject.toml
PyPIrich>=13.0.0pyproject.toml
PyPIaiofiles>=24.0.0pyproject.toml
PyPIpyyaml>=6.0.0pyproject.toml
PyPIpython-dotenv>=1.0.0pyproject.toml
PyPIpygments>=2.17.0pyproject.toml
PyPIwcwidth>=0.2.13pyproject.toml
PyPImistune>=3.0.2pyproject.toml
PyPIpillow>=11.0.0pyproject.toml
PyPItiktoken>=0.13.0pyproject.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

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.