aymericzip/intlayerNew scan
98/ 100 · A

Polished and well engineered. Punching above its star count.

Per-component Internationalisation solution for JS application. Type-Safe. Translate with AI. Edit Visually.

TypeScript772 starsApache-2.0updated today

Outstanding work. A score of 98/100 puts this repo in a very small tier of truly well-engineered open source projects.

DocumentationREADME, setup, examples, license
98
EngineeringTests, CI, linting, lockfiles
99
Project healthDescription, activity, stars, deps
97

What to fix first

The highest-impact improvements for this repo.

  1. 1
    CI/CD
    EngineeringInfo

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  2. 2
    CI/CD
    EngineeringInfo

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

  3. 3
    Reproducibility
    EngineeringIssue

    Add additional package-ecosystem entries (especially github-actions) to keep all dependencies current.

Detailed breakdown

Documentation

98
  • README100
    • README is present.
    • README is well structured with multiple sections.
    • README includes screenshots or visuals. Great for first impressions.
    • README has code examples.
    • README links to a live demo or deployed app.
    • README includes status badges.
  • Install and run instructions100
    • README documents how to install the project.
    • README documents how to run the project.
    • .env.example is present. Contributors can see exactly which env vars to set.
  • License100
    • Licensed under Apache-2.0.
  • Contributing guide84
    • Contributing guide is detailed and thorough.
    • Contributing guide includes setup/install instructions.
    • Contributing guide lacks a code style section (−8 pts).Describe your linting/formatting rules and how to run them.
    • Contributing guide lacks a testing section (−8 pts).Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    • Contributing guide describes the PR/review workflow.
    • Contributing guide includes code examples.
    • Optional: add a Code of Conduct.A CODE_OF_CONDUCT.md signals that your project is welcoming. GitHub has a template you can add in one click.

Engineering

99
  • Tests100
    • Test files detected (apps/app/src/utils/markdown.test.ts).
  • CI/CD100

    Not applicable?

    • CI is configured (.github/workflows/build_and_test.yaml).
    • CI workflow runs tests.
    • CI runs on pull requests, not just on pushes to main.
    • CI workflow runs a lint or format check.
    • Optional: add type checking to CI.Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
    • Optional: report test coverage in CI.Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
    • CI caches dependencies for faster runs.
    • CI tests across multiple environments or versions.
    • CI includes a build step.
  • Linting and formatting100
    • Linter or formatter configured (.prettierrc.json).
  • Reproducibility92
    • Lockfile present (bun.lock). Installs are reproducible.
    • Environment pinned via apps/app/Dockerfile.
    • Dependabot configured for npm.
    • Dependabot only covers one ecosystem (−8 pts). Covering 2+ ecosystems earns the full +20 pts.Add additional package-ecosystem entries (especially github-actions) to keep all dependencies current.
  • Issue and PR templates100
    • Issue or PR templates present.
    • Optional: add a SECURITY.md.A SECURITY.md explains how to responsibly disclose vulnerabilities. Worth adding once the project has real users.

Project health

97
  • Dependency manifest92
    • Dependency manifest found (package.json).
    • package.json has a description field.
    • package.json links back to the repository.
    • package.json has no keywords (−8 pts).Add a `keywords` array to help people find your package on npm.
  • Repository metadata100
    • Repository has a description.
    • Primary language detected: TypeScript.
  • Activity100
    • Actively maintained (pushed within the last month).
    • 772 stars.
  • Housekeeping100
    • .gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 121
    Forks
  • 300
    Releaseslatest 2y ago

Community

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

Responsiveness

  • 24d 22h
    Median issue response
  • <1h
    Median PR merge time
  • 15
    Open issues
Repository files34 root entries
  • .agents
    Good: Licensed under Apache-2.0.
  • .claude-plugin
  • .cursor
  • .github
    Good: CI is configured (.github/workflows/build_and_test.yaml).
    Good: Dependabot configured for npm.
    Good: Issue or PR templates present.
  • .husky
  • .vscode
  • apps
    Good: Test files detected (apps/app/src/utils/markdown.test.ts).
    Good: Environment pinned via apps/app/Dockerfile.
  • claude-plugins
  • compat
  • compat-comming
  • docs
  • examples
  • packages
  • plugins
  • scripts
  • utils
  • .biomeignore
  • .dockerignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .lintstagedrc
  • .prettierignore
  • .prettierrc.json
    Good: Linter or formatter configured (.prettierrc.json).
  • biome.json
  • bun.lock
    Good: Lockfile present (bun.lock). Installs are reproducible.
  • CLAUDE.md
  • commitlint.config.ts
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    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).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • LICENSE
  • package.json
    Good: Dependency manifest found (package.json).
  • 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.
  • temp.html
  • tsconfig.json
  • turbo.json