Upstream software project

ruby-pundit

OO authorization for Rails

About ruby-pundit

OO authorization for Rails

This project links 2 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

ruby-pundit repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 12 (Bookworm): 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.ruby-pundit: recorded package coverageDebian 12 (Bookworm)1 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
ruby-pundit
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
debian-12, opensuse-tumbleweed
License expression
MIT
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Object oriented authorization for Rails applications.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. Package ruby-pundit

    bookworm (Debian 12 (Bookworm)) (ruby): object oriented authorization for rails

    2.1.0-1: all

openSUSE Tumbleweed

  1. Package ruby4.0-rubygem-pundit

    tumbleweed (openSUSE Tumbleweed) (Unspecified): OO authorization for Rails

    2.4.0-1.8: x86_64

    Source: rubygem-pundit

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.