Pure-Rust, no_std collection of 30+ compression/decompression codecs (deflate, gzip, zlib, zstd, brotli, lzma/xz, lz4, bzip2, RAR, StuffIt, LHA, ARC, and more) behind one uniform streaming trait — each gated by its own Cargo feature. 100% safe (forbid(unsafe_code)), zero runtime deps.
KarpelesLab/compcol holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (90/100) and lowest on Community & Adoption (47/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.
81
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.
81
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)
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 69 is calibrated to 81 on the published index scale (record calibration 2026-08-02).
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.
API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20
MCP server — not applicable to this kind of software
40/40
Runnable examples — examples
Inputs used
example_dirs
examples
has_mcp_signal
no
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
10GitHub stars
2contributors
221commits, last 12 months
1days since last push
26releases
1bus factor
1open issues
crates.iopackage 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 crates:compcol@0.6.11; advisories assessed against the repository dependency graph instead
More detail
OpenSSF Scorecard 5.5 / 10
5.5aggregate
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-05 14:52 UTC
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.
Related records
Inspected repositories sharing catalogue tags or ecosystems with KarpelesLab/compcol. Read them side by side →
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.
