Weave Code
Code Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Laravel Passport Authorization Core Laravel Package

n3xt0r/laravel-passport-authorization-core

Core components for building OAuth2 authorization flows with Laravel Passport. Provides reusable helpers and abstractions to standardize consent/approval handling and authorization logic, making it easier to implement custom Passport authorization endpoints and UI.

View on GitHub
Deep Wiki
Context7
1.3.0

What's Changed

Added

  • Added Support for Laravel 13.

Full Changelog: https://github.com/N3XT0R/laravel-passport-authorization-core/compare/1.2.4...1.3.0

1.2.0

This release brings a major step forward in how authorization is understood, managed, and audited.
The focus is on clarity, safety, and transparency – especially in environments where users or service accounts act on behalf of different OAuth clients.


🔐 Client-aware permissions (no more guesswork)

Permissions are now explicitly tied to the OAuth client they belong to.

Instead of implicitly assuming where a permission applies, the system now clearly answers:

Who can do what – and in which client context?

This makes permission setups:

  • easier to understand
  • safer in multi-client environments
  • far more auditable

🧭 One clear authorization context

Authorization decisions are now based on a single, well-defined context:

  • the acting user or service account
  • the OAuth client it operates in

This removes hidden assumptions and ensures all permission checks rely on the same validated source of truth.


📣 Observable permission changes

Whenever permissions change, the system now emits clear domain events:

  • permissions assigned
  • permissions revoked
  • permissions updated

This makes authorization changes visible, traceable, and ready for:

  • audit logs
  • monitoring
  • external integrations

🧩 Clear use cases instead of hidden internals

Authorization management is now exposed through explicit application use cases instead of low-level storage access.

What this means:

  • easier and safer integration
  • predictable behavior
  • a stable API for UI layers and external systems

Read-only use cases make it possible to inspect clients, permissions, and grants without touching internal data structures.


🔄 Safer ownership changes

When the ownership of an OAuth client changes, all permissions of the previous owner are now automatically cleaned up.

This prevents:

  • stale permissions
  • unintended access
  • silent security issues

🐛 Fixes

  • Fixed an issue where scope strings could be generated incorrectly (e.g. resource.read instead of resource:read).

Result:
Authorization is now more explicit, more understandable, and much harder to misconfigure – whether you’re a developer, an administrator, or someone reviewing access rights.

Full Changelog: https://github.com/N3XT0R/laravel-passport-authorization-core/compare/1.1.0...1.2.0

Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
terminal42/code-quality-tools
codifyo/ts-generator-bundle
andydefer/laravel-cluster
testo/fiber
mintobit/jobqueue
a4sex/maintenance-bundle
a4sex/entity-date-update
a4sex/client-identifier
a4sex/base-utilites
a4sex/key-value-storage
a4sex/micro-status
chilldev/dependency-injection-extra
datinglibre/datinglibre-app-api
biberltd/corebundle
bricre/symfony-bundle-test
biberltd/logbundle
dominium/http-adapter-bundle
dominium/google-analytics
a4sex/auto-clean-entity
christhompsontldr/laravel-inky