Popular and well-maintained. A little polish away from elite status.

Reactive Programming in Swift

Documentation

85

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt80

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

78

CI/CD14pt57

CI is configured (.github/workflows/tests.yml).

Tests18pt80

Test files detected (RxExample/RxExample-iOSTests/CLLocationManager+RxTests.swift).

Reproducibility6pt80

Lockfile present (Gemfile.lock). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (.editorConfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

95

Activity5pt80

Actively maintained (pushed within 3 months).

Dependency manifest6pt100

Dependency manifest found (Gemfile).

Repository metadata5pt100

Repository has a description.

Housekeeping3pt100

.gitignore present.

Repository files38 root entries
  • .github
    Good: CI is configured (.github/workflows/tests.yml).
    Good: Issue or PR templates present.
  • assets
  • docs
  • Documentation
  • Platform
  • Preprocessor
  • Rx.playground
  • Rx.xcodeproj
  • Rx.xcworkspace
  • RxBlocking
  • RxCocoa
  • RxExample
    Good: Test files detected (RxExample/RxExample-iOSTests/CLLocationManager+RxTests.swift).
  • RxRelay
  • RxSwift
  • RxTest
  • scripts
  • Sources
  • Tests
  • .editorConfig
    Good: Linter or formatter configured (.editorConfig).
  • .gitignore
    Good: .gitignore present.
  • .jazzy.yml
  • .ruby-version
    Good: Environment pinned via .ruby-version.
  • .swift-version
  • .swiftformat
  • .swiftlint.yml
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • Dangerfile
  • default.profraw
  • Gemfile
    Good: Dependency manifest found (Gemfile).
  • Gemfile.lock
    Good: Lockfile present (Gemfile.lock). Installs are reproducible.
  • LICENSE.md
    Good: Licensed under MIT.
  • Makefile
  • mise.toml
  • Package.swift
  • Package@swift-5.9.swift
  • 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.
    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.
  • Version.xcconfig