Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 05:09 UTC

itlackey / openpalm

Personal AI assistant(s) powered by OpenCode

TypeScript · SvelteCustom license★ 35 stars⑂ 0 forkssince Feb 2026View on GitHub ↗
KindChat botDesktop applicationMCP serverCommand-line toolNetwork serviceLibraryhow this is determined
#ai-assistant#chatbot#discord-bot#docker#memory#opencode#self-hosted

itlackey/openpalm holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Vitality (86/100) and lowest on Security (38/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

IT LackeyPersonal account
37 followers83 public repossince Jan 2014Washington University in St. Louis

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
npmopenpalm0.13.62,1281754 days ago
npm@openpalm/guardian0.12.521245776 days ago
npm@openpalm/portal-sdk0.13.0-beta.1631365 days ago
npm@openpalm/slack-portal0.12.441242080 days ago
npm@openpalm/discord-portal0.12.448762080 days ago
npm@openpalm/lib0.12.5264912976 days ago
npm@openpalm/skeleton0.12.522475776 days ago
npm@openpalm/ui0.12.521,59712076 days ago

Metrics by category

Vitality

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

86Excellent · 21% of overall

Development activity

83Excellent
How it's scored
36/36Push recency — last push 4 days ago
19.4/36Commit cadence — 28/52 weeks with commits
18/18Commit volume — 3,748 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year3,748
human_commit_share0.94
days_since_last_push4
active_weeks_last_year28

Release discipline

90Excellent
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 4 days ago
27/27Release cadence — a release every ~2.8 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tag0.13.6
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases2.8

Community & Adoption

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

53Moderate · 17% of overall

Popularity & adoption

25At Risk
How it's scored
24.8/60Stars — 35 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars35
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

79Good
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateno

Ecosystem adoption (downloads)

63Moderate
How it's scored
50.2/80Monthly downloads — 5,808 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesopenpalm, @openpalm/guardian, @openpalm/portal-sdk, @openpalm/slack-portal, @openpalm/discord-portal, @openpalm/lib, @openpalm/skeleton, @openpalm/ui
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads5,808
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?

63Moderate · 23% of overall

Maintainer resilience (bus factor)

27At Risk
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
7/22.5Commit distribution — top contributor authored 69% of commits
5.4/13.5Contributor breadth — 4 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.689

Issue & PR responsiveness

82Excellent
How it's scored
40.9/42Issue resolution — 98% of issues closed
28.3/30PR acceptance — 385/408 decided PRs merged
13/13Newcomer PR acceptance — 2/2 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/15 approved changesets -- score normalized to 0
Inputs used
merged_prs385
open_issues7
closed_issues278
prs_merged_7d4
prs_decided_7d4
prs_merged_30d14
prs_decided_30d14
issue_closed_ratio0.975
closed_unmerged_prs23
first_time_authors_30d1
first_time_prs_merged_30d2
first_time_prs_decided_30d2

Ownership & stewardship

58Moderate
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
11.4/25Owner reach — 37 followers of itlackey
25/25Track record — 83 public repos, account ~12 yr old
Inputs used
followers37
owner_typeUser
is_verified—
owner_loginitlackey
public_repos83
account_age_days4,625
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 8 package(s) on npm
35/35Publish recency — latest publish 4 days ago
20/20Version history — 175 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesopenpalm, @openpalm/guardian, @openpalm/portal-sdk, @openpalm/slack-portal, @openpalm/discord-portal, @openpalm/lib, @openpalm/skeleton, @openpalm/ui
ecosystemsnpm
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall

Engineering practices

84Excellent
How it's scored
24/24CI workflows — 7 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 8 out of 8 merged PRs checked by a CI test -- score normalized to 10
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/10Topics — 7 topics
10/10Wiki
Inputs used
topicsai-assistant, chatbot, discord-bot, docker, memory, opencode, self-hosted
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?

38Weak · 16% of overall

Security posture

38Weak
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 8 out of 8 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/15 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
2/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 86 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate3.9

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.

80Excellent · 4% of overall

Agent context & guidance

100Exceptional
How it's scored
45/45Agent instructions — AGENTS.md, containers/assistant/AGENTS.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.docker.com/llms.txt)
40/40Legible commit history — 93 of 94 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.docker.com/llms.txt
legible_history_share0.989
agent_instruction_filesAGENTS.md, containers/assistant/AGENTS.md
agent_instruction_max_bytes21,453

Verify loop (build / test / typecheck)

64Moderate
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js
11/11Static type checking — packages/cli/tsconfig.json, packages/electron/tsconfig.json, packages/lib/tsconfig.json, packages/portal-sdk/tsconfig.json, packages/ui/tsconfig.json
10/10Reproducible environment — Dockerfile
10/10Demonstrated agent practice — 77 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configspackages/cli/tsconfig.json, packages/electron/tsconfig.json, packages/lib/tsconfig.json, packages/portal-sdk/tsconfig.json, packages/ui/tsconfig.json
agent_commit_share0.77
toolchain_manifests—
dependency_bot_commit_share0

Code legibility for models

100Exceptional
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.8/55Manageable file sizes — 4/904 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes74,227
source_files_sampled904
oversized_source_files4

Machine-readable interfaces

60Moderate
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalyes
api_schema_files—
interfaces_expected_ofchat-bot, network-service

Key facts

35GitHub stars
4contributors
3,748commits, last 12 months
4days since last push
100releases
1bus factor
7open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 3.9 / 10
3.9aggregate

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-09-15 05:09 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests8 out of 8 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/15 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
4Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities86 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
npmelectron-updater^6.8.9packages/electron/package.json
npm@modelcontextprotocol/sdk^1.30.0packages/guardian/package.json
npmdotenv^17.4.2packages/lib/package.json
npmmulticast-dns^7.2.5packages/lib/package.json
npmtar^7.5.22packages/lib/package.json
npmyaml^2.9.0packages/lib/package.json
npm@openpalm/portal-sdkworkspace:*packages/portal-discord/package.json
npmdiscord.js^14.27.0packages/portal-discord/package.json
npm@opencode-ai/sdk1.18.21packages/portal-sdk/package.json
npm@openpalm/portal-sdkworkspace:*packages/portal-slack/package.json
npm@slack/bolt^5.0.0packages/portal-slack/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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with itlackey/openpalm. Read them side by side →

94doobidoo/mcp-memory-serviceOpen-source persistent memory for AI agent pipelines (LangGraph, CrewAI, AutoGen) and Claude. REST API + knowledge graph + autonomous consolidation.Exceptional97appwrite/appwriteAppwrite® - complete cloud infrastructure for your web, mobile and AI apps. Including Auth, Databases, Storage, Functions, Messaging, Hosting, Realtime and moreExceptional97Stirling-Tools/Stirling-PDF#1 PDF Application on GitHub that lets you edit PDFs on any device anywhereExceptional97gptme/gptmeYour agent in your terminal, equipped with local tools: writes code, uses the terminal, browses the web. Make your own persistent autonomous agent on top!Exceptional96AstrBotDevs/AstrBotAI Agent Assistant & development framework that integrates lots of IM platforms, LLMs, plugins and AI feature, and can be your openclaw alternative. ✨Exceptional96yamadashy/repomix📦 Repomix is a powerful tool that packs your entire repository into a single, AI-friendly file. Perfect for when you need to feed your codebase to Large Language Models (LLMs) or other AI tools like Claude, ChatGPT, DeepSeek, Perplexity, Gemini, Gemma, Llama, Grok, and more.Exceptional

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 — npm.