Fine-grained RBAC and resource permission core for Node.js, with route permissions, data scopes, role inheritance, and wildcard matching.
Defines a CAIP-25 based endowment permission and helpers for interfacing with it
Implements the JSON-RPC methods for managing permissions as referenced in EIP-2255 and MIP-2 and inspired by MIP-5, but supporting chain-agnostic permission caveats in alignment with @metamask/multichain-api-middleware
Mediates access to JSON-RPC methods, used to interact with pieces of the MetaMask stack, via middleware for json-rpc-engine
`@bananapus/permission-ids-v6` is the shared constant library for Juicebox V6 operator permissions. It gives every repo in the ecosystem the same numeric meaning for the same permission name.
Common permission and authorization utilities for backend plugins
Isomorphic types and client for Backstage permissions and authorization
This is a pure-js JSON streaming parser for node.js
Controller with middleware for logging requests and responses to restricted and permissions-related methods
DES implementation
TypeScript definition for strtok3 token
The core SDK for CLI apps in the Zapier Developer Platform.
Extremely fast implementation of node core url library
Custom Playwright commands to inject axe-core and test for a11y
No description provided.
omggif is a JavaScript implementation of a GIF 89a encoder and decoder.
Core runtime for Destinations Actions.
Allows reading geolocation information from the device. Your app can poll for the current location or subscribe to location update events.
Defines a CAIP-25 based endowment permission and helpers for interfacing with it
Implements the JSON-RPC methods for managing permissions as referenced in EIP-2255 and MIP-2 and inspired by MIP-5, but supporting chain-agnostic permission caveats in alignment with @metamask/multichain-api-middleware
Permission types for the ERC-7715
Allow all policy backend module for the permission plugin.
No description provided.
https://github.com/deanm/css-color-parser-js
Basic functionality to work with shark permissions
Gritano::Core is a library that defines all Gritano's Models. It can be used to develop tools that manage users, repositories and permissions.
The win32-file-security library adds security related methods to the core File class for MS Windows. This includes the ability to get or set permissions, as well as encrypt or decrypt files.
This Gem provides a simple cli utility named `hyperctl` that can check the status of and [with appropriate permissions] enable/disable hyperthreading/SMT/sibling cores on Linux via the `sysfs` pseudo filesystem. It should be compatible with most modern Linux distributions as long as `sysfs` is mounted at `/sysfs`.
Turnitin Core API (TCA) provides direct API access to the core functionality provided by Turnitin. TCA supports file submission, similarity report generation, group management, and visualization of report matches via Cloud Viewer or PDF download. Below is the full flow to successfully set up an integration scope, an API Key, and make calls to TCA. Integration Scope and API Key management is done via the Admin Console UI by logging in as an admin user. For more details, go to our [developer portal documentation page](https://developers.turnitin.com/docs). ## Integration Scope and API Key Management TCA API calls must provide an API Key for authentication, so you must first have at least one integration scope associated with at least one API Key to use TCA. ### Admin Console UI First, login to Admin Console UI as an *Admin* user with permission to create Integration Scopes, under a tenant that is licensed to use the TCA product Integration Scopes (you can create a new one, or add keys to existing) * Click `Integrations` in the side bar --> `+ Add Integration` at top the top of the page --> Enter a name --> `Add` Button API Keys * Click `Integrations` in the side bar --> `Create API Key` Button next to a given Integration Scope --> Enter a name --> click `Create and View button` * Copy/Save the key manually or click save to clipboard button to copy it (this is the only time it will show) ## TCA Flow * Register a webhook * Create a submission * Upload a file for the submission * Wait for the submission upload to process * If you registered a webhook, a callback will be sent to it when upload is complete * The status of the *submission* will also update to `COMPLETE` * Request a Similarity Report * Wait for similarity report to process * If you registered a webhook, a callback will be sent to it when report is complete * The status of the *report* will also be updated to `COMPLETE` * Request a URL with parameters to view the Similarity Report
Manage your users' operations (permissions to execute some actions) in your application.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.