marin-community/marin

0

/ 100

Documentation77
Engineering100
Health89
Python1,129Apache-2.01d ago
Grade a repo

A well-known project done right. Strong docs and solid engineering throughout.

Open-source framework for the research and development of foundation models.

Documentation

77

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt52

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

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

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

100

Tests18pt100

Test files detected (experiments/datakit/store/ops/smoke_test.py).

CI/CD14pt100

CI is configured (.github/workflows/dupekit-unit.yaml).

Linting and formatting5pt100

Linter or formatter configured (infra/status-page/eslint.config.js).

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

89

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt86

Dependency manifest found (pyproject.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 133
    Forks
  • 15
    Releaseslatest 26d ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 1,129
    Watchers

Responsiveness

  • 735d 5h
    Median issue response
  • 23h
    Median PR merge time
  • 539
    Open issues
Repository files29 root entries
  • .agents
  • .claude
  • .github
    Good: CI is configured (.github/workflows/dupekit-unit.yaml).
    Good: Dependabot covers 2 ecosystems (uv, npm). Dependencies stay current.
    Good: Issue or PR templates present.
  • docker
  • docs
  • etc
  • experiments
    Good: Test files detected (experiments/datakit/store/ops/smoke_test.py).
    Good: Environment pinned via experiments/swe_rebench_trace/Dockerfile.
  • infra
    Good: Linter or formatter configured (infra/status-page/eslint.config.js).
  • lib
    Issue: Build artifacts or local files may be committed (lib/levanter/.idea/.gitignore) (−40 pts).Fix: Remove them and add to .gitignore.
  • scripts
  • tests
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • .pyrefly-baseline.json
  • .python-version
  • .readthedocs.yaml
  • AGENTS.md
  • AUTHORS.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +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.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • Makefile
  • mkdocs.yml
  • pr_reviews.db
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • 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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • TESTING.md
  • uv.lock
    Good: Lockfile present (uv.lock). Installs are reproducible.