roytam1/uxp

0

/ 100

Documentation53
Engineering48
Health100
C++68Other1d ago
Grade a repo

Getting some notice. Tests and CI would be the fastest wins.

UXP commits smorgasbord. Picking changes without removing XP/Vista and WebExtensions support. My custom changes will be in `custom` branch. Default `tracking` branch is not for compiling. Support requests should be raised in my blog comment forms below.

Documentation

53

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt55

This repository is large enough that GitHub truncated the file tree. The scan is based on a partial file list, so some checks may under-report.

Contributing guide5pt85

Contributing guide is detailed and thorough.

License6pt100

Licensed under Other.

Engineering

48

CI/CD14pt0

No CI configuration detected in this repository.

→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

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.

Reproducibility6pt70

Lockfile present (dom/media/test/external/requirements.txt). Installs are reproducible.

Tests18pt80

Test files detected (accessible/tests).

Linting and formatting5pt100

Linter or formatter configured (.eslintrc.js).

Project health

100

Dependency manifest6pt100

Dependency manifest found (build.gradle).

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

Community

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

Responsiveness

  • —
    Median issue response
  • 2h
    Median PR merge time
  • 9
    Open issues
Repository files51 root entries
  • accessible
    Good: Test files detected (accessible/tests).
  • application
  • build
  • caps
  • chrome
  • config
  • db
  • devtools
  • docs
    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.
    Good: Contributing guide describes code style expectations.
    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.
    Good: Code of conduct present.
  • docshell
  • dom
    Good: Lockfile present (dom/media/test/external/requirements.txt). Installs are reproducible.
  • editor
  • embedding
  • extensions
  • gfx
  • gradle
  • hal
  • image
  • intl
  • ipc
  • js
  • layout
  • .clang-format
  • .clang-format-ignore
  • .eslintignore
  • .eslintrc.js
    Good: Linter or formatter configured (.eslintrc.js).
  • .flake8
  • .gdbinit
  • .gdbinit_python
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .lldbinit
  • .taskcluster.yml
  • .ycm_extra_conf.py
  • aclocal.m4
  • Android.mk
  • AUTHORS
  • build.gradle
    Good: Dependency manifest found (build.gradle).
  • client.mk
  • client.py
  • CLOBBER
  • configure.in
  • configure.py
  • GNUmakefile
  • gradle.properties
  • gradlew
  • LEGAL
  • LICENSE
    Good: Licensed under Other.
  • Makefile.in
  • 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.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • SECURITY.md
    Good: Security policy present.