![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Oso is a batteries-included library for building authorization in your application.
Oso gives you a mental model and an authorization system – a set of APIs built on top of a declarative policy language called Polar, plus a debugger and REPL – to define who can do what in your application. You can express common concepts from “users can see their own data” and role-based access control, to others like multi-tenancy, organizations and teams, hierarchies and relationships.
Oso lets you offload the thinking of how to design authorization and build features fast, while keeping the flexibility to extend and customize as you see fit.
Developers can typically write a working Oso policy in <5 minutes, add Oso to an app in <30 minutes, and use Oso to solve real authorization problems within a few hours. To get started, you add the library to your application, create a new Oso instance and load an Oso policy. You can mix and match any of Oso’s authorization APIs to implement features like roles with custom policies that you write to suit your application.
Check out Use Cases to learn more about how teams are using Oso to build authorization.
Oso currently offers libraries for Node.js, Python, Go, Rust, Ruby, and Java.
To get up and running with Oso, check out the Getting Started guides in the Oso documentation.
If you have questions or need help getting started come chat with our engineering team & hundreds of other developers using Oso:
Oso's Rust core is developed against Rust's latest stable release.
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.
To work on a language library, you will need to meet the following version requirements:
See: CONTRIBUTING.md.
See: LICENSE.
We'd love to hear about your use case and experience with Oso. Share your story on Twitter or fill out this form for some Oso swag.
FAQs
oso authorization library.
The npm package oso receives a total of 1,432 weekly downloads. As such, oso popularity was classified as popular.
We found that oso demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 5 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.