ansible-collections/microsoft.iis

0

/ 100

Documentation86
Engineering41
Health53
PowerShell7GPL-3.01d ago
Grade a repo

Early stage. Tests, CI, and a strong README would raise this score quickly.

Documentation

86

Contributing guide5pt30

Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).

→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under GPL-3.0.

Engineering

41

Linting and formatting5pt0

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.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

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.

CI/CD14pt40

CI is configured (.github/workflows/docs-pr.yml).

Tests18pt80

Test files detected (tests).

Project health

53

Dependency manifest6pt0

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 metadata5pt40

No repository description set on GitHub (−60 pts).

→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.

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)
  • 14
    Forks
  • 6
    Releaseslatest 1mo ago

Community

  • 87% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 7
    Watchers

Responsiveness

  • 6d 3h
    Median issue response
  • <1h
    Median PR merge time
  • 8
    Open issues
Repository files16 root entries
  • .azure-pipelines
  • .github
    Good: CI is configured (.github/workflows/docs-pr.yml).
  • .vscode
  • changelogs
  • docs
  • meta
  • plugins
  • tests
    Good: Test files detected (tests).
  • .ansible-lint
  • .gitignore
    Good: .gitignore present.
  • CHANGELOG.rst
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • codecov.yml
  • COPYING
  • galaxy.yml
  • 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.