crossgl/crosstl

0

/ 100

Documentation94
Engineering82
Health100
Python346Apache-2.01d ago
Grade a repo

Polished and well engineered. Punching above its star count.

Universal Programming Language & Translator

Documentation

94

Contributing guide5pt80

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

82

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

Reproducibility6pt70

Lockfile present (requirements.txt). Installs are reproducible.

CI/CD14pt85

CI is configured (.github/workflows/backend-tests.yml).

Tests18pt100

Test files detected (crosstl/project/test_runner.py).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (requirements.txt).

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)
  • 85
    Forks
  • 5
    Releaseslatest 14d ago

Community

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

Responsiveness

  • 15h
    Median issue response
  • 3h
    Median PR merge time
  • 51
    Open issues
Repository files22 root entries
  • .github
    Good: CI is configured (.github/workflows/backend-tests.yml).
    Good: Issue or PR templates present.
  • crosstl
    Good: Test files detected (crosstl/project/test_runner.py).
  • demos
  • docs
  • examples
  • support
  • tests
  • tools
  • .gitignore
    Good: .gitignore present.
  • .pre-commit-config.yaml
  • .zenodo.json
  • CHANGELOG.md
  • CITATION.cff
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • deploy.sh
  • further-work-backlog.json
  • LICENSE
    Good: Licensed under Apache-2.0.
  • MANIFEST.in
  • 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.
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (requirements.txt).
  • setup.cfg
  • setup.py