hitachienergy / epiphany
Cloud and on-premises automation for Kubernetes centered industrial grade solutions.
hitachienergy/epiphany holds a health index of 19 out of 100, placing it in the Critical band. It scores highest on Sustainability & Governance (79/100) and lowest on Vitality (25/100). The repository is archived, so no further maintenance is expected.
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.
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 52 is calibrated to 53 on the published index scale (record calibration 2026-08-02).
Ownership
This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
Development activity
Work has arrived and nobody has attended to it
Silence alone is never the finding — a small, finished library may need no commits for years. This alert requires both: no human commit for a long time, and obligations the project is visibly not discharging. Automated commits do not count as maintenance.
How abandonment is assessedHow it's scored
| 0/36 | Push recency — last push 459 days ago |
| 0/36 | Commit cadence — 0/52 weeks with commits |
| 0/18 | Commit volume — 0 commits in the last year |
| 0/10 | OpenSSF Scorecard: Maintained — project is archived |
Inputs used
| commits_last_year | 0 |
| human_commit_share | 1 |
| days_since_last_push | 459 |
| active_weeks_last_year | 0 |
Release discipline
How it's scored
| 27/27 | Ships releases — 77 releases published |
| 7.2/36 | Release recency — latest release 464 days ago |
| 19.8/27 | Release cadence — a release every ~53.4 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 77 |
| latest_release_tag | v2.0.20 |
| releases_from_tags | no |
| days_since_latest_release | 464 |
| mean_days_between_releases | 53.4 |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
Popularity & adoption
How it's scored
| 34.9/60 | Stars — 142 stars |
| 16.8/25 | Forks — 105 forks |
| 0/15 | Watchers — 2 watchers |
Inputs used
| forks | 105 |
| stars | 142 |
| watchers | 2 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (Apache-2.0) |
| 0/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | yes |
| readme_badges | 8 |
| has_contributing | no |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | shields.io, sonarcloud.io |
| has_pull_request_template | no |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
How it's scored
| 36/54 | Bus factor — 3 contributor(s) cover half of all commits |
| 15.9/22.5 | Commit distribution — top contributor authored 29% of commits |
| 13.5/13.5 | Contributor breadth — 26 contributors |
| 10/10 | OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations |
Inputs used
| bus_factor | 3 |
| contributors_sampled | 26 |
| top_contributor_share | 0.293 |
Issue & PR responsiveness
How it's scored
| 42/42 | Issue resolution — 100% of issues closed |
| 27.1/30 | PR acceptance — 1,655/1,833 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 13.5/15 | OpenSSF Scorecard: Code-Review — Found 29/30 approved changesets -- score normalized to 9 |
Inputs used
| merged_prs | 1,655 |
| open_issues | 0 |
| closed_issues | 1,630 |
| prs_merged_7d | 0 |
| prs_decided_7d | 0 |
| prs_merged_30d | 0 |
| prs_decided_30d | 0 |
| issue_closed_ratio | 1 |
| closed_unmerged_prs | 178 |
| first_time_authors_30d | 0 |
| first_time_prs_merged_30d | 0 |
| first_time_prs_decided_30d | 0 |
Ownership & stewardship
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain — verified-domain status not read for this organization |
| 7.5/25 | Owner reach — 10 followers of hitachienergy |
| 17.2/25 | Track record — 28 public repos, account ~3 yr old |
Inputs used
| followers | 10 |
| owner_type | Organization |
| is_verified | — |
| owner_login | hitachienergy |
| public_repos | 28 |
| account_age_days | 1,193 |
Engineering Quality
Are baseline engineering and documentation practices in place?
Engineering practices
How it's scored
| 0/24 | CI workflows |
| 24/24 | Tests present |
| 16/16 | Linter config — .pylintrc, .rubocop.yml |
| 0/9.6 | Pre-commit hooks |
| 6.4/6.4 | .editorconfig |
| 0/20 | OpenSSF Scorecard: CI-Tests — 0 out of 30 merged PRs checked by a CI test -- score normalized to 0 |
Inputs used
| has_ci | no |
| has_tests | yes |
| has_editorconfig | yes |
| has_linter_config | yes |
| has_precommit_config | no |
Documentation
How it's scored
| 30/30 | README |
| 25/25 | Documentation directory |
| 0/15 | Documentation / homepage site |
| 10/10 | Repository description |
| 10/10 | Topics — 11 topics |
| 0/10 | Wiki |
Inputs used
| topics | kubernetes, docker, kafka, rabbitmq, elasticsearch, prometheus, infrastructure-as-code, ansible, terraform, keycloak, grafana |
| has_wiki | no |
| homepage | — |
| docs_site | — |
| has_readme | yes |
| has_docs_dir | yes |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
Security posture
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — no data |
| 0/2.5 | CI-Tests — 0 out of 30 merged PRs checked by a CI test -- score normalized to 0 |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 6.8/7.5 | Code-Review — Found 29/30 approved changesets -- score normalized to 9 |
| 2.5/2.5 | Contributors — project has 5 contributing companies or organizations |
| 0/10 | Dangerous-Workflow — no data |
| 7.5/7.5 | Dependency-Update-Tool — update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 0/7.5 | Maintained — project is archived |
| 0/5 | Packaging — no data |
| 0/5 | Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
| 0/5 | SAST — SAST tool is not run on all commits -- score normalized to 0 |
| 0/5 | Security-Policy — security policy file not detected |
| 0/7.5 | Signed-Releases — no data |
| 0/7.5 | Token-Permissions — no data |
| 0/7.5 | Vulnerabilities — 37 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 13 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 5 |
| scorecard_aggregate | 4 |
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.
Agent context & guidance
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 40/40 | Legible commit history — 96 of 100 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | 0.96 |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
Verify loop (build / test / typecheck)
How it's scored
| 18/18 | One-command bootstrap — docs/design-docs/modularization/cpt-tests/modules/AzureInfrastructure/Makefile, docs/design-docs/modularization/cpt-tests/modules/AzureInfrastructure/workdir/Makefile, docs/design-docs/modularization/cpt-tests/modules/BareMetalKafka/Makefile, docs/design-docs/modularization/cpt-tests/modules/BareMetalKafka/workdir/Makefile, docs/design-docs/modularization/cpt-tests/runs/infrastructure-and-kafka/Makefile |
| 22/22 | Automated tests |
| 11/11 | Lint / format config — .pylintrc, .rubocop.yml |
| 0/11 | Static type checking |
| 10/10 | Reproducible environment — devcontainer, Dockerfile, lockfile |
| 0/10 | Demonstrated agent practice — no agent-authored commits among the last 100 |
| 0/8 | Automated maintenance — no automated dependency updates observed |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | poetry.lock |
| has_dockerfile | yes |
| typed_language | no |
| bootstrap_files | docs/design-docs/modularization/cpt-tests/modules/AzureInfrastructure/Makefile, docs/design-docs/modularization/cpt-tests/modules/AzureInfrastructure/workdir/Makefile, docs/design-docs/modularization/cpt-tests/modules/BareMetalKafka/Makefile, docs/design-docs/modularization/cpt-tests/modules/BareMetalKafka/workdir/Makefile, docs/design-docs/modularization/cpt-tests/runs/infrastructure-and-kafka/Makefile |
| has_devcontainer | yes |
| has_linter_config | yes |
| typecheck_configs | — |
| agent_commit_share | 0 |
| toolchain_manifests | — |
| dependency_bot_commit_share | 0 |
Code legibility for models
How it's scored
| 0/45 | Type-checkable code — Python without a type-check config |
| 54.7/55 | Manageable file sizes — 1/174 source files over 60KB |
Inputs used
| primary_language | Python |
| largest_source_bytes | 528,733 |
| source_files_sampled | 174 |
| oversized_source_files | 1 |
Key facts
Data collection warnings
- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
- Could not fetch pypi package 'epiphany-devcon' from its registry
More detail
Star and fork history 0 ★ / 105 ⇿
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.
Each point covers 7 days.
OpenSSF Scorecard 4.0 / 10
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).
| 10 | Binary-Artifacts | no binaries found in the repo |
| n/a | Branch-Protection | internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md |
| 0 | CI-Tests | 0 out of 30 merged PRs checked by a CI test -- score normalized to 0 |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 9 | Code-Review | Found 29/30 approved changesets -- score normalized to 9 |
| 10 | Contributors | project has 5 contributing companies or organizations |
| n/a | Dangerous-Workflow | no workflows found |
| 10 | Dependency-Update-Tool | update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 0 | Maintained | project is archived |
| n/a | Packaging | packaging workflow not detected |
| 0 | Pinned-Dependencies | dependency not pinned by hash detected -- score normalized to 0 |
| 0 | SAST | SAST tool is not run on all commits -- score normalized to 0 |
| 0 | Security-Policy | security policy file not detected |
| n/a | Signed-Releases | no releases found |
| n/a | Token-Permissions | No tokens found |
| 0 | Vulnerabilities | 37 existing vulnerabilities detected |
Direct dependencies 9
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| PyPI | pyyaml | * | .devcontainer/pyproject.toml |
| PyPI | jinja2 | * | .devcontainer/pyproject.toml |
| PyPI | boto3 | * | .devcontainer/pyproject.toml |
| PyPI | jsonschema | * | .devcontainer/pyproject.toml |
| PyPI | python-json-logger | * | .devcontainer/pyproject.toml |
| PyPI | ruamel.yaml | * | .devcontainer/pyproject.toml |
| PyPI | click | * | .devcontainer/pyproject.toml |
| PyPI | ansible | ~9 | .devcontainer/pyproject.toml |
| PyPI | azure-cli | 2.63.0 | .devcontainer/pyproject.toml |
All dependencies 0
Full resolved dependency set from the GitHub dependency graph: 0 direct and 0 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|
Dependency advisories not assessed
Advisory matching could not run for this report: No resolved dependencies to assess
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.
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.31.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics.