Solid engineering. The main gap is visibility.

Fluent UI web represents a collection of utilities, React components, and web components for building web applications.

Documentation

75

Install and run instructions9pt45

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

Add a section showing how to install dependencies.

Contributing guide5pt72

CONTRIBUTING guide found.

README12pt85

README is present.

License6pt100

Licensed under Other.

Engineering

87

CI/CD14pt57

CI is configured (.github/workflows/check-packages.yml).

Reproducibility6pt92

Lockfile present (yarn.lock). Installs are reproducible.

Tests18pt100

Test files detected (apps/react-18-tests-v8/jest.config.js).

Linting and formatting5pt100

Linter or formatter configured (.eslintrc.json).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

60

Activity5pt5

No pushes in over 2 years. Looks unmaintained (−95 pts).

A recent commit signals the project is alive and worth using.

Repository metadata5pt60

Repository has a description.

Dependency manifest6pt85

Dependency manifest found (package.json).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 1
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • Median issue response
  • Median PR merge time
  • 0
    Open issues
Repository files61 root entries
  • .codesandbox
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .devops
  • .githooks
  • .github
    Good: CI is configured (.github/workflows/check-packages.yml).
    Good: Dependabot configured for npm.
    Good: Issue or PR templates present.
  • .storybook
  • .vscode
  • .yarn
  • apps
    Good: Test files detected (apps/react-18-tests-v8/jest.config.js).
  • change
  • ghdocs
  • packages
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
  • rfcs
  • scripts
  • specs
  • tools
  • typings
  • .babelrc-v9.json
  • .eslintrc.json
    Good: Linter or formatter configured (.eslintrc.json).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gulp.js
  • .npmrc
  • .nxignore
  • .prettierignore
  • .yarnrc
  • azure-pipelines.bundlesize.yml
  • azure-pipelines.hotfix.yml
  • azure-pipelines.perf-test.yml
  • azure-pipelines.release-fluentui.yml
  • azure-pipelines.release-vnext-nightly.yml
  • azure-pipelines.release-vnext.yml
  • azure-pipelines.release.yml
  • azure-pipelines.vrt-baseline.yml
  • azure-pipelines.vrt-pr.yml
  • azure-pipelines.yml
  • babel.config.js
  • beachball.config.js
  • dangerfile.js
  • gulpfile.ts
  • jest.config.ts
  • jest.preset.js
  • lage.config.js
  • lerna.json
  • LICENSE
    Good: Licensed under Other.
  • lint-staged.config.js
  • migrations.json
  • nx.json
  • package.json
    Good: Dependency manifest found (package.json).
  • prettier.config.js
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    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.
    Good: README includes status badges.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • sizeauditor.json
  • tsconfig.base.all.json
  • tsconfig.base.json
  • tsconfig.base.v0.json
  • tsconfig.base.v8.json
  • tsconfig.json
  • workspace.json
  • yarn-ci.sh
  • yarn.lock
    Good: Lockfile present (yarn.lock). Installs are reproducible.