Solid engineering. The main gap is visibility.

๐Ÿž๐ŸŽจ Full-featured photo image editor using canvas. It is really easy, and it comes with great filters.

Documentation

97

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Contributing guide5pt100

Contributing guide is detailed and thorough.

Engineering

79

CI/CD14pt40

CI is configured (.github/workflows/detectRuntimeError.yml).

Reproducibility6pt70

Lockfile present (package-lock.json). Installs are reproducible.

Tests18pt100

Test files detected (test).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

74

Repository metadata5pt60

Repository has a description.

Activity5pt60

Last pushed 3-6 months ago (โˆ’40 pts). A push within 90 days earns 80 pts; within 30 days earns 100 pts.

โ†’ A recent commit keeps the project looking alive to visitors and contributors.

Dependency manifest6pt83

Dependency manifest found (package.json).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • โ€”
    Commits (30d / 90d)
  • 0
    Forks
  • 0
    Releases

Community

  • โ€”
    Community health
  • โ€”
    authors own >50% of commits
  • 0
    Watchers

Responsiveness

  • โ€”
    Median issue response
  • โ€”
    Median PR merge time
  • 17
    Open issues
Repository files28 root entries
  • .github
    Good: CI is configured (.github/workflows/detectRuntimeError.yml).
    Good: Issue or PR templates present.
  • docs
  • examples
  • src
  • test
    Good: Test files detected (test).
  • .babelrc
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .eslintignore
  • .eslintrc.js
  • .gitignore
    Good: .gitignore present.
  • .prettierrc
  • bower.json
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • createConfigVariable.js
  • index.d.ts
  • ISSUE_TEMPLATE.md
  • jsdoc.conf.json
  • karma.conf.js
  • LICENSE
    Good: Licensed under MIT.
  • makesvg.js
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • 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.
  • tsBannerGenerator.js
  • tslint.json
  • tuidoc.config.json
  • webpack.config.js