Oso
What is Oso?
Oso is a batteries-included framework for building authorization in your application.
With Oso, you can:
- Model: Set up common permissions patterns like role-based access control (RBAC) and relationships using Oso’s built-in primitives. Extend them however you need with Oso’s declarative policy language, Polar.
- Filter: Go beyond yes/no authorization questions. Implement authorization over collections too - e.g., “Show me only the records that Juno can see.”
- Test: Write unit tests over your authorization logic now that you have a single interface for it. Use the Oso debugger or REPL to track down unexpected behavior.
Oso offers libraries for Node.js, Python, Go, Rust, Ruby, and Java.
Our latest creation Oso Cloud makes authorization across services as easy as oso.authorize(user, action, resource). Learn about it.
Documentation
- To get up and running with Oso, try the Getting Started guide.
- Full documentation is available at docs.osohq.com.
- Check out Use Cases to learn more about how teams are using Oso in production.
- To learn about authorization best practices (not specific to Oso), read the Authorization Academy guides.
Community & Support
If you have any questions on Oso or authorization more generally, you can join our engineering team & hundreds of other developers using Oso in our community Slack:
Share your story
We'd love to hear about your use case and experience with Oso. Share your story in our Success Stories issue.
Development
Core
Oso's Rust core is developed against Rust's latest stable release.
Language libraries
Oso's language libraries can be developed without touching the Rust core, but you will still need the Rust stable toolchain installed in order to build the core.
To build the WebAssembly core for the Node.js library, you will need to have
wasm-pack installed and available on your system PATH.
Language requirements
To work on a language library, you will need to meet the following version requirements:
- Java: 11+
- Maven: 3.6+
- Node.js: 12.20.0+
- Yarn 1.22+
- Python: 3.7+
- Ruby: 2.4+
- Bundler 2.1.4+
- Rust: 1.46+
- Go: 1.14+
Contributing & Jobs
See: CONTRIBUTING.md.
If you want to work on the Oso codebase full-time, visit our jobs page.
License
See: LICENSE.
Release files for django-oso 0.27.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_oso-0.27.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / django_oso-0.27.0-py3-none-any.whl
| Download URL | django_oso-0.27.0-py3-none-any.whl |
|---|---|
| Size | 12.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d959a3d74817fd07633e55b982fc7d0c6b7377f48f1c34fea435e22a588750b1
|
|
BLAKE2b-256 checksum How to use checksums |
296696f55957680fb7397976b16d0198f31dffa117440800bb7072cdabb67279
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.16
|
Security for django-oso 0.27.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
