dicklesworthstone/frankenpandasNew scan
99/ 100 · A

Well engineered for its size. A portfolio piece worth showing off.

Memory-safe, clean-room Rust reimplementation of pandas with packetized conformance gates, strict/hardened runtime modes, and RaptorQ-backed artifact durability.

Rust15 starsOtherupdated today

Outstanding work. A score of 99/100 puts this repo in a very small tier of truly well-engineered open source projects.

DocumentationREADME, setup, examples, license
97
EngineeringTests, CI, linting, lockfiles
99
Project healthDescription, activity, stars, deps
100

What to fix first

The highest-impact improvements for this repo.

  1. 1
    CI/CD
    EngineeringInfo

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

  2. 2
    Install and run instructions
    DocumentationIssue

    Add a .env.example listing all required environment variables so contributors know what to set up.

  3. 3
    Reproducibility
    EngineeringIssue

    Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.

Detailed breakdown

Documentation

97
  • README100
    • README is present.
    • README is well structured with multiple sections.
    • README includes screenshots or visuals. Great for first impressions.
    • README has code examples.
    • README links to a live demo or deployed app.
    • README includes status badges.
  • Install and run instructions90
    • README documents how to install the project.
    • README documents how to run the project.
    • No .env.example found (−10 pts).Add a .env.example listing all required environment variables so contributors know what to set up.
  • License100
    • Licensed under Other.
  • Contributing guide100
    • Contributing guide is detailed and thorough.
    • Contributing guide includes setup/install instructions.
    • Contributing guide describes code style expectations.
    • Contributing guide explains how to run tests.
    • Contributing guide describes the PR/review workflow.
    • Contributing guide includes code examples.
    • Optional: add a Code of Conduct.A CODE_OF_CONDUCT.md signals that your project is welcoming. GitHub has a template you can add in one click.

Engineering

99
  • Tests100
    • Test files detected (crates/fp-conformance/oracle/tests).
    • Rust workspace with test files detected. Run with `cargo test --workspace`.
  • CI/CD100

    Not applicable?

    • CI is configured (.github/workflows/ci.yml).
    • CI workflow runs tests.
    • CI runs on pull requests, not just on pushes to main.
    • CI workflow runs a lint or format check.
    • CI runs type checking (tsc, mypy, cargo check, etc.).
    • Optional: report test coverage in CI.Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
    • CI tests across multiple environments or versions.
  • Linting and formatting100
    • Rust linting configured (.editorconfig, cargo clippy in CI, cargo fmt in CI).
  • Reproducibility90
    • Lockfile present (Cargo.lock). Installs are reproducible.
    • No Dockerfile or runtime version pin found. Adding one earns +10 pts.Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
    • Dependabot covers 2 ecosystems (cargo, github-actions). Dependencies stay current.
  • Issue and PR templates100
    • Issue or PR templates present.
    • Security policy present.

Project health

100
  • Dependency manifest100
    • Dependency manifest found (Cargo.toml).
    • Cargo.toml is a workspace manifest for a multi-crate Rust project.
  • Repository metadata100
    • Repository has a description.
    • Primary language detected: Rust.
  • Activity100
    • Actively maintained (pushed within the last month).
    • 15 stars so far.
  • Housekeeping100
    • .gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 5
    Forks
  • 44
    Releaseslatest 2mo ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 15
    Watchers

Responsiveness

  • 20h
    Median issue response
  • 11h
    Median PR merge time
  • 0
    Open issues
Repository files49 root entries
  • .beads
    Good: .gitignore present.
  • .bench-history
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot covers 2 ecosystems (cargo, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • artifacts
  • benches
  • crates
    Good: Test files detected (crates/fp-conformance/oracle/tests).
  • docs
  • fuzz
  • githooks
  • references
  • reports
  • scripts
  • tests
  • .editorconfig
    Good: Rust linting configured (.editorconfig, cargo clippy in CI, cargo fmt in CI).
  • .gitattributes
  • .gitignore
  • .mailmap
  • .skill-loop-progress.md
  • AGENTS.md
  • AUTHORS.md
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CATEGORICAL_COVERAGE.md
  • CHANGELOG.md
  • CITATION.cff
  • COMPREHENSIVE_SPEC_FOR_FRANKENPANDAS_V1.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • COVERAGE_MATRIX.md
  • deny.toml
  • DIFFERENTIAL_FUZZ_DESIGN.md
  • ERROR_CONFORMANCE.md
  • EXHAUSTIVE_LEGACY_ANALYSIS.md
  • EXISTING_PANDAS_STRUCTURE.md
  • FEATURE_PARITY.md
  • frankenpandas_illustration.webp
  • LICENSE
    Good: Licensed under Other.
  • PANIC_CONTRACT_COVERAGE.md
  • PARITY-COVERAGE.md
  • PHASE2C_EXTRACTION_PACKET.md
  • PLAN_TO_PORT_PANDAS_TO_RUST.md
  • PROPOSED_ARCHITECTURE.md
  • 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.
  • release-plz.toml
  • REVIEW_SESSION_HANDOFF.md
  • rust-toolchain.toml
  • rustfmt.toml
  • SECURITY.md
    Good: Security policy present.
  • TODO_EXECUTION_TRACKER.md
  • UPGRADE_LOG.md