loopdive/js2
Grade a repo

0

/ 100

GradeA

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

ECMAScript to WebAssembly GC AOT compiler

Documentation83
Engineering98
Health94
TypeScript17Apache-2.0today

Documentation

83

README12pt70

README is present.

Contributing guide5pt80

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

98

Reproducibility6pt80

Lockfile present (pnpm-lock.yaml). Installs are reproducible.

Tests18pt100

Test files detected (.github/cla/cla-gate.test.mjs).

CI/CD14pt100

CI is configured (.github/workflows/ci-status-basic.yml).

Linting and formatting5pt100

Linter or formatter configured (.prettierrc).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (package.json).

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)
  • 2
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 17
    Watchers

Responsiveness

  • 9h
    Median issue response
  • <1h
    Median PR merge time
  • 2
    Open issues
Repository files47 root entries
  • .claude
  • .codex
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .github
    Good: Test files detected (.github/cla/cla-gate.test.mjs).
    Good: CI is configured (.github/workflows/ci-status-basic.yml).
    Good: Issue or PR templates present.
  • .husky
  • .vscode
  • bench
  • benchmarks
  • docs
  • examples
  • packages
  • plan
  • public
  • scripts
  • spec-compliance
  • src
  • tests
    Issue: Build artifacts or local files may be committed (tests/fixtures/npm-resolve/node_modules/@scope) (−40 pts).Fix: Remove them and add to .gitignore.
  • website
  • .git-commit-msg
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .mcp.json
  • .npmignore
  • .prettierignore
  • .prettierrc
    Good: Linter or formatter configured (.prettierrc).
  • AGENTS.md
  • biome.json
  • CHANGELOG.md
  • CLA.md
  • CLAUDE.md
  • CODEOWNERS
  • 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.
  • jsr.json
  • LICENSE
    Good: Licensed under Apache-2.0.
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Good: README has code examples.
    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.
    Good: README documents how to run the project.
  • ROADMAP.md
  • STATUS.md
  • test262
  • tsconfig.json
  • vite.config.lib.ts
  • vite.config.ts
  • vitest.config.ts
  • WORKFLOW.md