oracle/oci-python-sdk

0

/ 100

Documentation66
Engineering43
Health100
Python473Other1d ago
Grade a repo

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

Oracle Cloud Infrastructure SDK for Python

Documentation

66

README12pt40

README is present.

Contributing guide5pt47

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

43

CI/CD14pt0

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.

Linting and formatting5pt0

No linter or formatter configured.

→ Add [tool.ruff] to pyproject.toml. Ruff handles linting and formatting in one tool and replaces flake8, isort, and black.

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.

Reproducibility6pt80

Lockfile present (requirements.txt). Installs are reproducible.

Tests18pt90

Test files detected (src/oci/ai_language/models/test_and_validation_dataset_strategy.py).

Project health

100

Dependency manifest6pt100

Dependency manifest found (pyproject.toml).

Repository metadata5pt100

Repository has a description.

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)
  • 319
    Forks
  • 389
    Releaseslatest 8y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 473
    Watchers

Responsiveness

  • 10h
    Median issue response
  • <1h
    Median PR merge time
  • 93
    Open issues
Repository files23 root entries
  • docs
  • examples
    Good: Environment pinned via examples/Resource_Principle_v2.2_Functions_example/Dockerfile.
  • scripts
  • src
    Good: Test files detected (src/oci/ai_language/models/test_and_validation_dataset_strategy.py).
  • tests
  • .gitignore
    Good: .gitignore present.
  • .readthedocs.yml
  • CHANGELOG.rst
  • CONTRIBUTING.rst
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • LICENSE.txt
    Good: Licensed under Other.
  • MANIFEST.in
  • NOTICE.txt
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • README-development.rst
    Good: README is present.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • README.rst
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
  • SECURITY.md
    Good: Security policy present.
  • setup.cfg
  • setup.py
  • THIRD_PARTY_LICENSES_DEV.txt
  • THIRD_PARTY_LICENSES.txt
  • tox.ini
  • wercker.yml