Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-17 19:36 UTC

manrajgrover / halo

💫 Beautiful spinners for terminal, IPython and Jupyter

PythonMIT★ 3,023 stars⑂ 149 forkssince Sep 2017View on GitHub ↗

manrajgrover/halo holds a health index of 36 out of 100, placing it in the Weak band. It scores highest on Community & Adoption (87/100) and lowest on Security (1/100). It was last updated 823 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 45 is calibrated to 42 on the published index scale (record calibration 2026-08-02).

Ownership

Manraj SinghPersonal account
842 followers234 public repossince Oct 2013@media-net

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
PyPIhalo0.0.31836,707312137 days agoconsoleloadingindicatorprogressclispinnerspinnersterminaltermbusywaitidle

Metrics by category

Vitality

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

1Critical · 21% of overall
How it's scored
0/36Push recency — last push 823 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push823
active_weeks_last_year0
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

Community & Adoption

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

87Excellent · 17% of overall
How it's scored
56.5/60Stars — 3,023 stars
18.1/25Forks — 149 forks
7.2/15Watchers — 21 watchers
Inputs used
forks149
stars3,023
watchers21
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateyes
has_code_of_conductno
readme_badge_servicesci.appveyor.com, coveralls.io, shields.io, travis-ci.com
has_pull_request_templateyes
How it's scored
79/80Monthly downloads — 836,707 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageshalo
dependents—
ecosystemspypi
total_downloads—
monthly_downloads836,707
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?

58Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5.2/22.5Commit distribution — top contributor authored 77% of commits
13.5/13.5Contributor breadth — 23 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled23
top_contributor_share0.767
How it's scored
24.2/42Issue resolution — 58% of issues closed
24.5/30PR acceptance — 76/93 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs76
open_issues33
closed_issues45
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.577
closed_unmerged_prs17
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
21/25Owner reach — 842 followers of manrajgrover
25/25Track record — 234 public repos, account ~12 yr old
Inputs used
followers842
owner_typeUser
is_verified—
owner_loginmanrajgrover
public_repos234
account_age_days4,722
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
4/35Publish recency — latest publish 2,137 days ago
20/20Version history — 31 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageshalo
ecosystemspypi
any_deprecatedno
min_days_since_publish2,137

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — .pylintrc, tox.ini
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 7 topics
10/10Wiki
Inputs used
topicshalo, spinner, python, jupyter, ora, ipython, async
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?

1Critical · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestsrequirements-dev.txt, requirements.txt, setup.cfg, setup.py
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. 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.

44Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
18.7/40Legible commit history — 35 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.35
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .pylintrc, tox.ini
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/19 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes21,267
source_files_sampled19
oversized_source_files0
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, notebooks
Inputs used
example_dirsexamples, notebooks
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

3,023GitHub stars
23contributors
0commits, last 12 months
823days since last push
0releases
1bus factor
33open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

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

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.

050100150145252017-102022-032026-08

Each point covers 9 days.

All dependencies 10

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

RegistryPackageVersionRelation
PyPIcolorama—indirect
PyPIcoverage—indirect
PyPIlog-symbols—indirect
PyPIpylint—indirect
PyPIpytest—indirect
PyPIsix—indirect
PyPIspinners—indirect
PyPItermcolor—indirect
PyPItox—indirect
PyPItwine—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.