parseablehq/parseable
Grade a repo

0

/ 100

GradeC

Good community traction and solid fundamentals. Nearly in the top tier.

Top 38% of 5,156 graded repos

Parseable is an observability datalake built from first principles.

Documentation97
Engineering59
Health86
Rust2,391AGPL-3.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

15 to address
  1. 1
    Tests18pt

    Add integration tests in a tests/ directory or unit tests via #[cfg(test)] blocks.

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

97

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt97

Contributing guide is detailed and thorough.

README12pt100

README is present.

License6pt100

Licensed under AGPL-3.0.

Engineering

59

Linting and formatting5pt0

No Rust linting or formatting enforced.

→ Add `cargo clippy -- -D warnings` and `cargo fmt --check` as CI steps, and optionally a rustfmt.toml for project-specific style rules.

Tests18pt55

Cargo.toml has dev-dependencies (may include test tooling).

CI/CD14pt57

CI is configured (.github/workflows/build-push-edge-debug.yaml).

Reproducibility6pt80

Lockfile present (Cargo.lock). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

86

Dependency manifest6pt55

Dependency manifest found (Cargo.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 166
    Forks
  • 92
    Releaseslatest 3y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 2,391
    Watchers

Responsiveness

  • 8d 8h
    Median issue response
  • <1h
    Median PR merge time
  • 31
    Open issues
Repository files37 root entries
  • .github
    Good: CI is configured (.github/workflows/build-push-edge-debug.yaml).
    Good: Issue or PR templates present.
  • helm
  • helm-releases
  • resources
  • scripts
  • src
  • systemd
  • .deepsource.toml
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • about.hbs
  • about.toml
  • build.rs
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CITATION.cff
  • CNAME
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • Cross.toml
  • docker-compose-distributed-test-with-kafka.yaml
  • docker-compose-distributed-test.yaml
  • docker-compose-gcs-distributed-test.yaml
  • docker-compose-local.yaml
  • docker-compose-test-with-kafka.yaml
  • docker-compose-test.yaml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • Dockerfile.debug
  • Dockerfile.dev
  • Dockerfile.kafka
  • helm-reindex.sh
  • index.yaml
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • Makefile
  • parseable-ingest-haproxy.cfg
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • USERS.md
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/parseablehq/parseable)](https://www.repo-grade.com/report/parseablehq/parseable)

More graded Rust repos