Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 10:45 UTC

liam0205 / pineapple

Multi-runtime DAG pipeline engine — declare in Python, execute in Go / Java / Python, decouple with JSON.

Go · C++ · JavaApache-2.0★ 11 stars⑂ 1 forksince Apr 2026View on GitHub ↗

liam0205/pineapple holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on AI Readiness (92/100) and lowest on Security (1/100). It was last updated today. A single contributor accounts for most of its recent work.

59
overall / 100
Moderate

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.

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

Ownership

LiamPersonal account
604 followers83 public repossince Jan 2013@tuna @kwai @CTeX-org @Lightspeed-Intelligence

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 publish
Gogithub.com/Liam0205/pineapple/pine-gov0.10.12-311 day ago
Mavenpage.liam:pine0.10.12-301 day ago
PyPIpineapple-apple0.10.121,621721 day ago

Metrics by category

Vitality

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

78Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
9.7/36Commit cadence14/52 weeks with commits
18/18Commit volume942 commits in the last year
0/10OpenSSF Scorecard: Maintainedno data
Inputs used
commits_last_year942
human_commit_share
days_since_last_push0
active_weeks_last_year14
How it's scored
16.2/27Ships releases69 version tags (no GitHub releases)
36/36Release recencylatest release 1 days ago
27/27Release cadencea release every ~3.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count69
latest_release_tagv0.10.12
releases_from_tagsyes
days_since_latest_release1
mean_days_between_releases3.5

Community & Adoption

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

32At Risk · 17% of overall
How it's scored
16.2/60Stars11 stars
0/25Forks1 forks
0/15Watchers0 watchers
Inputs used
forks1
stars11
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

64Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.3/22.5Commit distributiontop contributor authored 99% of commits
4.1/13.5Contributor breadth3 contributors
0/10OpenSSF Scorecard: Contributorsno data
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.986
How it's scored
37.5/42Issue resolution89% of issues closed
27.1/30PR acceptance93/103 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Reviewno data
Inputs used
merged_prs93
open_issues7
closed_issues58
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.892
closed_unmerged_prs10
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
20/25Owner reach604 followers of Liam0205
25/25Track record83 public repos, account ~13 yr old
Inputs used
followers604
owner_typeUser
is_verified
owner_loginLiam0205
public_repos83
account_age_days4,923
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable3 package(s) on go, maven, pypi
35/35Publish recencylatest publish 1 days ago
20/20Version history72 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/Liam0205/pineapple/pine-go, page.liam:pine, pineapple-apple
ecosystemsgo, maven, pypi
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

82Excellent · 19% of overall
How it's scored
24/24CI workflows8 workflow(s)
24/24Tests present
16/16Linter config.golangci.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics12 topics
10/10Wiki
Inputs used
topicsdag, data-pipeline, dsl, hot-reload, lua, operator-framework, parallel-computing, pipeline-engine, python, java, multi-runtime, go
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_diryes
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 lockfilespublished library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilesgo.sum
manifestspine-go/go.mod, pine-java/pom.xml, pyproject.toml
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.

92Excellent · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes3,435
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
18/18One-command bootstrapMakefile, pine-go/Makefile
22/22Automated tests
11/11Lint / format config.golangci.yml
11/11Static type checkingGo (statically typed)
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile, pine-go/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeGo (statically typed)
54.6/55Manageable file sizes3/402 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes75,360
source_files_sampled402
oversized_source_files3
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

11GitHub stars
3contributors
942commits, last 12 months
0days since last push
69releases
1bus factor
7open issues
Go, Maven, PyPIpackage ecosystems

Data collection warnings

  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

Direct dependencies 8
RegistryPackageVersion constraintManifest
Gogithub.com/Liam0205/wangshuv0.2.0pine-go/go.mod
Gogithub.com/alicebob/miniredis/v2v2.37.0pine-go/go.mod
Gogithub.com/redis/go-redis/v9v9.18.0pine-go/go.mod
Gogithub.com/yuin/gopher-luav1.1.2pine-go/go.mod
Mavencom.fasterxml.jackson.core:jackson-databind${jackson.version}pine-java/pom.xml
Mavenorg.luaj:luaj-jse3.0.1pine-java/pom.xml
Mavenorg.apache.bcel:bcel6.10.0pine-java/pom.xml
Mavenredis.clients:jedis5.1.0pine-java/pom.xml
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.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsGo, Maven, PyPI.