Getting noticed, but rough fundamentals could turn visitors away.
A public version to sync with SupportArticles-docs-pr
Documentation
26
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
Licensed under CC-BY-4.0.
Engineering
24
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
CI is configured (.github/workflows/validate_branch_names.yml).
Issue or PR templates present.
Project health
58
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 1,184Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 235Watchers
Responsiveness
- —Median issue response
- 5hMedian PR merge time
- 26Open issues
Repository files34 root entries
- .githubGood: CI is configured (.github/workflows/validate_branch_names.yml).Good: Issue or PR templates present.
- Exchange
- includes
- Microsoft365
- Office
- Outlook
- SharePoint
- SkypeForBusiness
- support
- Teams
- templates
- Viva
- windows
- .acrolinx-config.edn
- .gitattributes
- .gitignoreGood: .gitignore present.
- .openpublishing.publish.config.json
- .openpublishing.redirection.developer.json
- .openpublishing.redirection.exchange.json
- .openpublishing.redirection.json
- .openpublishing.redirection.microsoft365.json
- .openpublishing.redirection.office.json
- .openpublishing.redirection.outlook.json
- .openpublishing.redirection.sharepoint.json
- .openpublishing.redirection.skypeforbusiness.json
- .openpublishing.redirection.teams.json
- .openpublishing.redirection.viva.json
- azure-pipelines.yml
- CODEOWNERS
- LICENSEGood: Licensed under CC-BY-4.0.
- LICENSE-CODE
- README.mdGood: README is present.Issue: README is very short (−20 pts). 400+ characters earns +10 pts; 1,500+ earns +20 pts.Fix: Add an Overview, Install, Usage, and Contributing section at minimum.Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.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.mdGood: Security policy present.
- ThirdPartyNotices.md