dicklesworthstone/franken_networkx

0

/ 100

Documentation90
Engineering84
Health100
Python7Other1d ago
Grade a repo

Polished work that hasn't found its audience yet.

Memory-safe clean-room Rust reimplementation of NetworkX with deterministic graph semantics, differential conformance, and RaptorQ-backed durability.

Documentation

90

Contributing guide5pt53

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

This repository is large enough that GitHub truncated the file tree. The scan is based on a partial file list, so some checks may under-report.

License6pt100

Licensed under Other.

Engineering

84

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Reproducibility6pt70

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

Tests18pt100

Test files detected (crates/fnx-algorithms/tests).

CI/CD14pt100

CI is configured (.github/workflows/ci.yml).

Linting and formatting5pt100

Rust linting configured (.ruff.toml, cargo clippy in CI, cargo fmt in CI).

Project health

100

Dependency manifest6pt100

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)
  • 2
    Forks
  • 1
    Releaseslatest 3d ago

Community

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

Responsiveness

  • —
    Median issue response
  • —
    Median PR merge time
  • 0
    Open issues
Repository files25 root entries
  • .beads
    Good: .gitignore present.
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • artifacts
  • crates
    Good: Test files detected (crates/fnx-algorithms/tests).
  • docs
  • examples
  • fuzz
  • .gitignore
  • .ruff.toml
    Good: Rust linting configured (.ruff.toml, cargo clippy in CI, cargo fmt in CI).
  • .skill-loop-progress.md
  • AGENTS.md
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG.md
  • COMPREHENSIVE_SPEC_FOR_FRANKENNETWORKX_V1.md
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • EXHAUSTIVE_LEGACY_ANALYSIS.md
  • EXISTING_NETWORKX_STRUCTURE.md
  • FEATURE_PARITY.md
  • franken_networkx_illustration.webp
  • LICENSE
    Good: Licensed under Other.
  • PLAN_TO_PORT_NETWORKX_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.
  • SECURITY.md
    Good: Security policy present.