Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 06:50 UTC

Martian-Engineering / lossless-claw

Lossless Claw — LCM (Lossless Context Management) plugin for OpenClaw

TypeScriptMIT★ 4,894 stars⑂ 444 forkssince Feb 2026View on GitHub ↗
KindLibraryCommand-line toolTerminal interfacehow this is determined

Martian-Engineering/lossless-claw holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (90/100) and lowest on Security (42/100). It was last updated today. A single contributor accounts for most of its recent work.

80
overall / 100
Excellent

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.

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

Ownership

145 followers40 public repossince Sep 2024

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@martian-engineering/lossless-claw0.15.68,012600 days agoopenclawopenclaw-plugincontext-managementllmsummarizationconversation-memorydag
Gogithub.com/Martian-Engineering/lossless-clawv0.15.6-480 days ago

Metrics by category

Vitality

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

90Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
19.4/36Commit cadence28/52 weeks with commits
18/18Commit volume598 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year598
human_commit_share0.92
days_since_last_push0
active_weeks_last_year28

Release discipline

100Exceptional
How it's scored
27/27Ships releases45 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~1.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count45
latest_release_tagv1.0.0-beta.7
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases1.1
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

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

69Good · 17% of overall
How it's scored
59.8/60Stars4,894 stars
22.1/25Forks444 forks
7.5/15Watchers23 watchers
Inputs used
forks444
stars4,894
watchers23
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
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
How it's scored
52.1/80Monthly downloads8,012 downloads/month across go, npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@martian-engineering/lossless-claw, github.com/Martian-Engineering/lossless-claw
dependents
ecosystemsgo, npm
total_downloads
monthly_downloads8,012
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?

65Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.7/22.5Commit distributiontop contributor authored 52% of commits
13.5/13.5Contributor breadth88 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled88
top_contributor_share0.524
How it's scored
28.1/42Issue resolution67% of issues closed
24.1/30PR acceptance483/602 decided PRs merged
13/13Newcomer PR acceptance11/11 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 7/25 approved changesets -- score normalized to 2
Inputs used
merged_prs483
open_issues158
closed_issues319
prs_merged_7d26
prs_decided_7d26
prs_merged_30d54
prs_decided_30d55
issue_closed_ratio0.669
closed_unmerged_prs119
first_time_authors_30d7
first_time_prs_merged_30d11
first_time_prs_decided_30d11
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
15.6/25Owner reach145 followers of Martian-Engineering
15.7/25Track record40 public repos, account ~1 yr old
Inputs used
followers145
owner_typeOrganization
is_verifiedno
owner_loginMartian-Engineering
public_repos40
account_age_days716

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable2 package(s) on go, npm
35/35Publish recencylatest publish 0 days ago
20/20Version history60 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@martian-engineering/lossless-claw, github.com/Martian-Engineering/lossless-claw
ecosystemsgo, npm
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

67Good · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests28 out of 28 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
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?

42Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests28 out of 28 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 7/25 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 4 contributing companies or organizations
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 3 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
2.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
0/5SASTSAST tool is not run on all commits -- score normalized to 0
2/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities18 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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.

83Excellent · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history90 of 92 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.978
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes4,219
How it's scored
18/18One-command bootstraptui/Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checkingtsconfig.json
10/10Reproducible environmentDockerfile, lockfile
10/10Demonstrated agent practice5 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
5/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum, package-lock.json
has_dockerfileyes
typed_languageyes
bootstrap_filestui/Makefile
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0.05
toolchain_manifeststui/go.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
50.3/55Manageable file sizes22/258 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes204,375
source_files_sampled258
oversized_source_files22

Key facts

4,894GitHub stars
88contributors
598commits, last 12 months
0days since last push
45releases
1bus factor
158open issues
Go, 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
  • deps.dev does not index npm:@martian-engineering/lossless-claw@0.15.6; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 444 ⇿
0Stars
444Forks
43Releases

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.

0100200300400500441552026-022026-052026-08
Major 0Minor 13Patch 22
OpenSSF Scorecard 4.2 / 10
4.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-28 06:49 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests28 out of 28 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 7/25 approved changesets -- score normalized to 2
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
0SASTSAST tool is not run on all commits -- score normalized to 0
4Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities18 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
npm@sinclair/typebox0.34.48package.json
Gogithub.com/charmbracelet/bubblesv1.0.0tui/go.mod
Gogithub.com/charmbracelet/bubbleteav1.3.10tui/go.mod
Gogithub.com/charmbracelet/lipglossv1.1.0tui/go.mod
Gogithub.com/muesli/reflowv0.3.0tui/go.mod
Gomodernc.org/sqlitev1.45.0tui/go.mod
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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm, Go.