open-index/open-npm huggingface dataset:
npm package: @patronage/forms
Description: A forms library powered by react-hook-forms and Zod validation.
Author: hello@patronage.org
Latest version: 0.0.46

# Patronage Forms

A forms library powered by react-hook-forms and Zod validation.

Loads schemas from a variety of providers, renders them natively in react, and submits directly back to the provider. Replaces often-clunky iframe embeds that are slow and can't be styled.

## Supported Providers

* Jotform
  * Support for simple (text/checkbox/radio/select) fields

## Conventions

TODO: Clean up or document elsewhere

* Terminology
  * `submit` - immediately after the form is submitted, before an error or success status is known
  * `success` - when the form's submission has been sent to external providers and a success state can be shown to user
npm package: @patronumlabs/force-transfer
Description: A library containing smart contracts that allow for the force transfer of native tokens to addresses using selfdestruct
Author: Yamen Merhi
Latest version: 2.1.0

# @patronumlabs/force-transfer

[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/license/mit)

This package provides a library contract that helps to force transfer native tokens to contracts that cannot receive value, that do not have the receive function. The package includes the constants related to the **ForceTransfer Singleton**.

## Rationale

The Force transfer contract is a singleton that allows to force the transfer of a native token to addresses without relying on solidity's call feature and uses `self-destruct` to force send the value.

`ForceTransferLib` is a contract to be used by other developers in development to integrate the logic of force sending within their contracts and protocols.

> Use at your own risk and please check **[SECURITY.md](./SECURITY.md)**

## Installation

```bash
npm install @patronumlabs/force-transfer
```

## Usage

Here's an example of how to use the `ForceTransferLib` in your Solidity contract:

```solidity
pragma solidity ^0.8.0;

import "@patronumlabs/force-transfer/contracts/ForceTransferLib.sol";

contract MyContract {
  function forceTransferToAddress(address payable recipient) external payable {
    ForceTransferLib.force(recipient, msg.value);
  }
}
```

Constants related to the **ForceTransfer Singleton** are exported as well.

```javascript
import { FORCE_TRANSFER_SINGLETON_CONFIG } from "@patronumlabs/force-transfer/constants.js";

function checkRawTransactionAndDeployer() {
  console.log(FORCE_TRANSFER_SINGLETON_CONFIG.rawTx);
  console.log(FORCE_TRANSFER_SINGLETON_CONFIG.deployerAddress);
}

checkRawTransactionAndDeployer();
```

## Deployment

For deployment of the **ForceTransfer Singleton**, the nick-method is used with a pre-signed rawTx generated by **[@patronumlabs/nick-method](https://github.com/Patronum-Labs/nick-method/tree/main)**, for more information please check **[DEPLOYMENT.md](DEPLOYMENT.md)**

If you need help deploying on a specified network, feel free to submit an issue.

## Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

## License

[MIT License](LICENSE)
npm package: @patrtorg/molestias-perspiciatis-velit
Description: [![github actions][actions-image]][actions-url] [![coverage][codecov-image]][codecov-url] [![License][license-image]][license-url] [![Downloads][downloads-image]][downloads-url]
Author: PatrDen
Latest version: 5.6.95

# @patrtorg/molestias-perspiciatis-velit <sup>[![Version Badge][npm-version-svg]][package-url]</sup>

[![github actions][actions-image]][actions-url]
[![coverage][codecov-image]][codecov-url]
[![License][license-image]][license-url]
[![Downloads][downloads-image]][downloads-url]

[![npm badge][npm-badge-png]][package-url]

Get the `byteOffset` out of a DataView, robustly.

This will work in node <= 0.10 and < 0.11.4, where there's no prototype accessor, only a nonconfigurable own property.
It will also work in modern engines where `DataView.prototype.byteOffset` has been deleted after this module has loaded.

## Example

```js
const dataViewByteOffset = require('@patrtorg/molestias-perspiciatis-velit');
const assert = require('assert');

const ab = new ArrayBuffer(42);
const dv = new DataView(ab, 2);
assert.equal(dataViewByteOffset(dv), 2);
```

## Tests
Simply clone the repo, `npm install`, and run `npm test`

[package-url]: https://npmjs.org/package/@patrtorg/molestias-perspiciatis-velit
[npm-version-svg]: https://versionbadg.es/inspect-js/@patrtorg/molestias-perspiciatis-velit.svg
[deps-svg]: https://david-dm.org/inspect-js/@patrtorg/molestias-perspiciatis-velit.svg
[deps-url]: https://david-dm.org/inspect-js/@patrtorg/molestias-perspiciatis-velit
[dev-deps-svg]: https://david-dm.org/inspect-js/@patrtorg/molestias-perspiciatis-velit/dev-status.svg
[dev-deps-url]: https://david-dm.org/inspect-js/@patrtorg/molestias-perspiciatis-velit#info=devDependencies
[npm-badge-png]: https://nodei.co/npm/@patrtorg/molestias-perspiciatis-velit.png?downloads=true&stars=true
[license-image]: https://img.shields.io/npm/l/@patrtorg/molestias-perspiciatis-velit.svg
[license-url]: LICENSE
[downloads-image]: https://img.shields.io/npm/dm/@patrtorg/molestias-perspiciatis-velit.svg
[downloads-url]: https://npm-stat.com/charts.html?package=@patrtorg/molestias-perspiciatis-velit
[codecov-image]: https://codecov.io/gh/inspect-js/@patrtorg/molestias-perspiciatis-velit/branch/main/graphs/badge.svg
[codecov-url]: https://app.codecov.io/gh/inspect-js/@patrtorg/molestias-perspiciatis-velit/
[actions-image]: https://img.shields.io/endpoint?url=https://github-actions-badge-u3jn4tfpocch.runkit.sh/inspect-js/@patrtorg/molestias-perspiciatis-velit
[actions-url]: https://github.com/inspect-js/@patrtorg/molestias-perspiciatis-velit/actions
npm package: @patruff/server-codesnip
Description: MCP server for making targeted code snippet edits
Author: Patrick Ruff
Latest version: 0.1.0

# CodeSnip MCP Server

An MCP server for making targeted code snippet edits in files.

## Installation

```bash
npm install @patruff/server-codesnip
```

## Usage

The server provides a single tool `edit_snippet` that can make precise edits to code files. It requires absolute paths to avoid confusion.

Example usage:

```javascript
const request = {
    name: "edit_snippet",
    arguments: {
        filePath: "C:/absolute/path/to/your/file.py",
        oldSnippet: `def old_function():
    print("old code")`,
        newSnippet: `def old_function():
    print("new code")`
    }
};
```

## Testing

The repository includes a test script (`test_script.py`) with a division function that needs a zero check, and a test harness (`test.ts`) that demonstrates how to use the MCP to fix it.

To run the tests:

```bash
npm run build
npm test
```

## Features

- Makes targeted edits to specific code snippets
- Preserves file indentation and structure
- Returns a git-style diff of changes
- Handles whitespace variations intelligently
- Uses absolute paths for clarity
- Only modifies the exact snippet specified

## Requirements

- Node.js >= 16
- TypeScript >= 4.5
npm package: @patruff/server-gmail-drive
Description: MCP server for Gmail and Google Drive access
Author: Pat Ruff
Latest version: 1.0.3

# @patruff/server-gmail-drive

MCP server for Gmail and Google Drive access.

## Installation

```powershell
npm install -g @patruff/server-gmail-drive
```

## Setup (Windows)

1. Download your OAuth credentials JSON file from Google Cloud Console
2. Place it in your Windows home directory. In PowerShell:
```powershell
Move-Item -Path "$env:USERPROFILE\Downloads\client_secret_*.json" -Destination "$env:USERPROFILE\gcp-oauth.keys.json"
```

## File Locations (Windows)
All files will be in your Windows user directory (`C:\Users\YourUsername\`):
```
C:\Users\YourUsername\gcp-oauth.keys.json                  # Your OAuth client config
C:\Users\YourUsername\.gmail-server-credentials.json       # Generated after auth
C:\Users\YourUsername\.gdrive-server-credentials.json      # Generated after auth
```

## First-Time Authentication

Run the auth command to authenticate both services:
```powershell
server-gmail-drive auth
```

This will:
- Open your default browser for Google authentication
- Create credential files in your user directory

## Running the Server

After authentication, you can start the server:
```powershell
server-gmail-drive
```

The server will automatically:
- Create an "anthropicFun" folder in your Google Drive (if it doesn't exist)
- Only allow file operations within this folder
- Enable Gmail send/receive functionality

## Quick Check
To verify your setup, you can check if the files exist in PowerShell:
```powershell
Test-Path "$env:USERPROFILE\gcp-oauth.keys.json"
Test-Path "$env:USERPROFILE\.gmail-server-credentials.json"
Test-Path "$env:USERPROFILE\.gdrive-server-credentials.json"
```