Rough and inactive. Tests, CI, and a fuller README would revive it.
Input plugin of Azure Monitor Logs for Fluentd
Documentation
74
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.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
38
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.
No RuboCop config found.
→ Add a .rubocop.yml and run `rubocop` in CI to enforce consistent Ruby style.
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.
Lockfile present (Gemfile.lock). Installs are reproducible.
Test files detected (test).
Project health
75
No pushes in over 2 years. Looks unmaintained (−95 pts).
→ A recent commit signals the project is alive and worth using.
Dependency manifest found (Gemfile).
Repository has a description.
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 5Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 7Watchers
Responsiveness
- —Median issue response
- 5d 10hMedian PR merge time
- 1Open issues
Repository files10 root entries
- lib
- testGood: Test files detected (test).
- .gitignoreGood: .gitignore present.
- fluent-plugin-azuremonitorlog.gemspec
- GemfileGood: Dependency manifest found (Gemfile).
- Gemfile.fluentd.0.12
- Gemfile.lockGood: Lockfile present (Gemfile.lock). Installs are reproducible.
- LICENSEGood: Licensed under MIT.
- Rakefile
- README.mdGood: 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.Good: README has code examples.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.Good: README documents how to install the project.Good: README documents how to run the project.