ttanasart-pt/pixel-composer

0

/ 100

Documentation53
Engineering29
Health94
Game Maker Language1,296MIT1d ago
Grade a repo

Real traction, but rough engineering makes it hard for contributors to trust.

Node base VFX editor for pixel art.

Documentation

53

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

Install and run instructions9pt45

README documents how to install the project.

README12pt58

README is present.

License6pt100

Licensed under MIT.

Engineering

29

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

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.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

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.

CI/CD14pt100

CI is configured (docsdata/.github/workflows/pages.yml).

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (extensions/Steamworks/steamworks_windows/Steamworks.sln).

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)
  • 78
    Forks
  • 3
    Releaseslatest 1mo ago

Community

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

Responsiveness

  • 6h
    Median issue response
  • —
    Median PR merge time
  • 64
    Open issues
Repository files27 root entries
  • animcurves
  • datafiles
  • datasrc
    Issue: Build artifacts or local files may be committed (datasrc/__pycache__/update.cpython-313.pyc) (−40 pts).Fix: Remove them and add to .gitignore.
  • docs
  • docsdata
    Good: CI is configured (docsdata/.github/workflows/pages.yml).
  • extensions
    Good: Dependency manifest found (extensions/Steamworks/steamworks_windows/Steamworks.sln).
  • fonts
  • img
  • notes
  • objects
  • options
  • releases
  • rooms
  • scripts
  • shaders
  • sprites
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • LICENSE
    Good: Licensed under MIT.
  • PixelComposer.code-workspace
  • PixelComposer.resource_order
  • PixelComposer.yyp
  • PixelComposer.yyp.css
  • pre_build_step.bat
  • pre_run.bat
  • README.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    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.
  • README.md.backup