Public record
Software health reportschema 0.30.0 · metrics 2.10.0 · 2026-08-04 05:45 UTC

proma-ai / Proma

Proma brings a seamless general-purpose Agent experience to your workflow. Built for 100× professionals and the proactive Agent era, it supports Claude and Pi runtimes, Feishu group chats, and any LLM provider.

TypeScriptAGPL-3.0★ 1,905 stars⑂ 233 forkssince Jan 2026View on GitHub ↗
KindDesktop applicationMCP serverCommand-line toolhow this is determined

proma-ai/Proma holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Vitality (86/100) and lowest on Security (32/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Proma AIOrganization
10 followers1 public reposince May 2026

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?

86Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
19.4/36Commit cadence28/52 weeks with commits
18/18Commit volume1,601 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 17 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,601
human_commit_share1
days_since_last_push0
active_weeks_last_year28
How it's scored
27/27Ships releases82 releases published
36/36Release recencylatest release 1 days ago
27/27Release cadencea release every ~1.8 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count82
latest_release_tagv0.16.8
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases1.8

Community & Adoption

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

64Moderate · 17% of overall
How it's scored
53.2/60Stars1,905 stars
19.7/25Forks233 forks
3.9/15Watchers6 watchers
Inputs used
forks233
stars1,905
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (AGPL-3.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
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?

48Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6/22.5Commit distributiontop contributor authored 74% of commits
13.5/13.5Contributor breadth19 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled19
top_contributor_share0.735
How it's scored
29.2/42Issue resolution70% of issues closed
24.9/30PR acceptance877/1,058 decided PRs merged
6.5/13Newcomer PR acceptance1/2 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 8/30 approved changesets -- score normalized to 2
Inputs used
merged_prs877
open_issues100
closed_issues229
prs_merged_7d51
prs_decided_7d60
prs_merged_30d51
prs_decided_30d60
issue_closed_ratio0.696
closed_unmerged_prs181
first_time_authors_30d2
first_time_prs_merged_30d1
first_time_prs_decided_30d2
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
7.5/25Owner reach10 followers of proma-ai
2.5/25Track record1 public repos, account ~0 yr old
Inputs used
followers10
owner_typeOrganization
is_verified
owner_loginproma-ai
public_repos1
account_age_days65
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

69Good · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 28 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://proma.cool/download
10/10Repository description
10/10Topics8 topics
10/10Wiki
Inputs used
topicsagent, agent-sdk, agents, chatbot, chatgpt, claude, gemini, llm
has_wikiyes
homepagehttps://proma.cool/download
docs_sitehttps://proma.cool/download
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

32At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0/2.5CI-Tests0 out of 28 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
1.5/7.5Code-ReviewFound 8/30 approved changesets -- score normalized to 2
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 17 issue activity found in the last 90 days -- score normalized to 10
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-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities162 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate3.2
Excluded from scoring (no data or not applicable): Packaging. 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.

59Moderate · 4% of overall
How it's scored
45/45Agent instructions.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc, AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_files.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc, AGENTS.md, CLAUDE.md
agent_instruction_max_bytes26,600
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingapps/cli/tsconfig.json, apps/electron/tsconfig.json, packages/core/tsconfig.json, packages/session-core/tsconfig.json, packages/shared/tsconfig.json, packages/ui/tsconfig.json, tsconfig.json
0/10Reproducible environment
2/10Demonstrated agent practice1 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
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configsapps/cli/tsconfig.json, apps/electron/tsconfig.json, packages/core/tsconfig.json, packages/session-core/tsconfig.json, packages/shared/tsconfig.json, packages/ui/tsconfig.json, tsconfig.json
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
53.8/55Manageable file sizes16/726 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes185,157
source_files_sampled726
oversized_source_files16
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs
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

1,905GitHub stars
19contributors
1,601commits, last 12 months
0days since last push
82releases
1bus factor
100open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package '@proma/cli' from its registry
  • Could not fetch npm package '@proma/ui' from its registry
  • Could not fetch npm package '@proma/core' from its registry
  • Could not fetch npm package '@proma/shared' from its registry
  • Could not fetch npm package '@proma/session-core' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 233 ⇿
0Stars
233Forks
81Releases

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.

0408012016020024023062026-022026-052026-08
Major 0Minor 10Patch 71
OpenSSF Scorecard 3.2 / 10
3.2aggregate

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

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 28 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 8/30 approved changesets -- score normalized to 2
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 17 issue activity found in the last 90 days -- score normalized to 10
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
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities162 existing vulnerabilities detected
Direct dependencies 27
RegistryPackageVersion constraintManifest
npmjotai^2.17.1package.json
npm@proma/session-coreworkspace:*apps/cli/package.json
npm@proma/sharedworkspace:*apps/cli/package.json
npm@anthropic-ai/claude-agent-sdk0.3.201apps/electron/package.json
npm@anthropic-ai/sdk^0.93.0apps/electron/package.json
npm@earendil-works/pi-agent-core0.82.1apps/electron/package.json
npm@earendil-works/pi-ai0.82.1apps/electron/package.json
npm@earendil-works/pi-coding-agent0.82.1apps/electron/package.json
npm@fontsource-variable/inter5.2.8apps/electron/package.json
npm@modelcontextprotocol/sdk^1.29.0apps/electron/package.json
npm@pierre/diffs^1.1.20apps/electron/package.json
npm@xmldom/xmldom^0.8.11apps/electron/package.json
npmadm-zip^0.5.17apps/electron/package.json
npmdompurify^3.4.5apps/electron/package.json
npmiconv-lite^0.6.3apps/electron/package.json
npmmammoth^1.12.0apps/electron/package.json
npmpdfjs-dist^4.10.38apps/electron/package.json
npmsharp^0.35.3apps/electron/package.json
npmtypebox1.1.38apps/electron/package.json
npm@proma/sharedworkspace:*packages/core/package.json
npmhighlight.js^11.11.1packages/core/package.json
npmshiki^3.22.0packages/core/package.json
npm@proma/sharedworkspace:*packages/session-core/package.json
npm@proma/coreworkspace:*packages/ui/package.json
npmbeautiful-mermaid1.1.3packages/ui/package.json
npmmermaid11.15.0packages/ui/package.json
npmshiki^3.22.0packages/ui/package.json
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.30.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics.