iann0036/iam-dataset
Grade a repo

0

/ 100

GradeD

Popular for its size, but the engineering basics lag behind the interest.

A consolidated series of structured data for cloud identity and access management systems, including datasets for AWS, Azure, and Google Cloud

Documentation51
Engineering61
Health94
Python323MITtoday

Documentation

51

Install and run instructions9pt0

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

→ Add a section showing how to install dependencies.

README12pt55

README is present.

Contributing guide5pt77

CONTRIBUTING guide found.

License6pt100

Licensed under MIT.

Engineering

61

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/data.yml).

Tests18pt80

Test files detected (util/aws_js/node_modules/available-typed-arrays/test).

Reproducibility6pt80

Lockfile present (util/aws_js/package-lock.json). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (util/aws_js/node_modules/available-typed-arrays/.eslintrc).

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (util/aws_js/node_modules/available-typed-arrays/package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 38
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 323
    Watchers

Responsiveness

  • 16h
    Median issue response
  • 4h
    Median PR merge time
  • 10
    Open issues
Repository files9 root entries
  • .github
    Good: CI is configured (.github/workflows/data.yml).
  • aws
  • azure
  • gcp
  • util
    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.
    Good: Code of conduct present.
    Good: Test files detected (util/aws_js/node_modules/available-typed-arrays/test).
    Good: Linter or formatter configured (util/aws_js/node_modules/available-typed-arrays/.eslintrc).
    Good: Lockfile present (util/aws_js/package-lock.json). Installs are reproducible.
    Good: Environment pinned via util/aws_js/node_modules/is-generator-function/.nvmrc.
    Good: Dependency manifest found (util/aws_js/node_modules/available-typed-arrays/package.json).
    Issue: Build artifacts or local files may be committed (util/aws_js/node_modules/.bin) (−40 pts).Fix: Remove them and add to .gitignore.
  • .gitignore
    Good: .gitignore present.
  • LICENSE
    Good: Licensed under MIT.
  • NOTICE
  • 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.