open-index/open-npm huggingface dataset:
npm package: @fieldmade/ui
Description: This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).
Latest version: 1.5.8

# Getting Started with Create React App

This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).

## Available Scripts

In the project directory, you can run:

### `yarn docs`

Runs the storybook.

### `yarn build:docs`

Builds the storybook.

### `yarn codegen`

generates the code for the Tailwind Unique util.

### `yarn test`

Launches the test runner in the interactive watch mode.\
See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.

### `yarn build`

Builds the app for production to the `build` folder.\
npm package: @fieldproxyfp/ui-components
Description: This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).
Author: Karan
Latest version: 1.0.3

# Getting Started with Create React App

This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).

## Available Scripts

In the project directory, you can run:

### `yarn start`

Runs the app in the development mode.\
Open [http://localhost:3000](http://localhost:3000) to view it in the browser.

The page will reload if you make edits.\
You will also see any lint errors in the console.

### `yarn test`

Launches the test runner in the interactive watch mode.\
See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.

### `yarn build`

Builds the app for production to the `build` folder.\
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.\
Your app is ready to be deployed!

See the section about [deployment](https://facebook.github.io/create-react-app/docs/deployment) for more information.

### `yarn eject`

**Note: this is a one-way operation. Once you `eject`, you can’t go back!**

If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

## Learn More

You can learn more in the [Create React App documentation](https://facebook.github.io/create-react-app/docs/getting-started).

To learn React, check out the [React documentation](https://reactjs.org/).
npm package: @fieldtech/simple-conventional-changelog
Description: Simple Commitizen adapter following the conventional-changelog format.
Author: Justina Chen
Latest version: 1.1.5

# simple-conventional-changelog

[![license](https://img.shields.io/github/license/mashape/apistatus.svg)](https://github.com/FieldTech/simple-conventional-changelog)
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
[![npm version](https://img.shields.io/npm/v/@fieldtech/simple-conventional-changelog/latest.svg)](https://www.npmjs.org/package/@fieldtech/simple-conventional-changelog)
[![npm downloads](https://img.shields.io/npm/dm/@fieldtech/simple-conventional-changelog.svg)](http://npm-stat.com/charts.html?package=@fieldtech/simple-conventional-changelog&from=2020-04-02)
[![Build Status](https://www.travis-ci.org/FieldTech/simple-conventional-changelog.svg?branch=master)](https://www.travis-ci.org/FieldTech/simple-conventional-changelog)

作为 [X-Developer](https://x-developer.cn) 生产力工具家族成员，Simple Conventional Changelog 简化了 [commitizen](https://github.com/commitizen/cz-cli) 的提交步骤，并提供了中文支持。

基于 [conventional changelog](https://github.com/conventional-changelog/conventional-changelog) 但实现了更简单的注释风格，仅需一行，如下所示：

```
#123 feat 中文交互式支持
```

此适配器生成的 `Git` 注释完整兼容 [X-Developer](https://x-developer.cn) 对 `Git` 仓库的数据分析。

## 安装

`commitizen` 提供了交互式命令行，来生成格式化的 `Git` 注释，运行以下命令进行安装。

```
$ npm install -g commitizen
```

## 配置

### 生成配置

进入您的 `Git仓库` 目录，非 `node.js` 项目，需运行以下命令创建 `package.json` 文件。

```
$ npm init --yes
```

随后运行以下命令即启用 simple-conventional-changelog 风格的提交规范。

```
$ commitizen init @fieldtech/simple-conventional-changelog --save --save-exact
```

检查 `package.json` 可看到下面的生成项。

```json5
{
    "config": {
        "commitizen": {
            "path": "./node_modules/@fieldtech/simple-conventional-changelog"
        }
    }
}
```

### 个性化配置

此为可选项，可以通过更改以下的 `key` 值进行个性化配置。

- maxHeaderWidth：注释行的最大长度
- defaultType：默认的提交类型
- defaultSubject：默认注释
- defaultIssues：默认任务编号


```json5
{
// ...  默认参数值
    "config": {
        "commitizen": {      
            "path": "./node_modules/@fieldtech/simple-conventional-changelog",
            "maxHeaderWidth": 100,
            "defaultType": "",     
            "defaultSubject": "",
            "defaultIssues": ""
        }
    }
// ...    
}
```

## 提交代码

使用 `git cz` 而非 `git commit` 来提交变更。随后您将看到交互式操作界面，根据提示即可完成规范的注释提交。

```
$ git cz
```

## 参考

- [X-Developer](https://x-developer.cn)
npm package: @fieldtest/core
Description: Open source validation toolkit for data pipelines, APIs, and integrations. Built with TypeScript for modern development workflows.
Author: Matthew Hendricks
Latest version: 1.0.2

# FieldTest Core

**FieldTest** is a framework-agnostic TypeScript validation toolkit for Markdown and Standard Schema. It helps you catch content errors at build time, with strong TypeScript support and clear diagnostics.

## Install

```bash
npm install @fieldtest/core
# or
pnpm add @fieldtest/core
```

## Quick Example

```ts
import { loadUserSchema, parseMarkdown, validateWithSchema, z } from "@fieldtest/core";

const blogSchema = z.object({
  title: z.string(),
  date: z.string(),
  tags: z.array(z.string()).optional(),
});

const schema = loadUserSchema(blogSchema);
const doc = parseMarkdown(`---\ntitle: Hello\ndate: 2025-01-01\n---\nContent`);
const result = await validateWithSchema(schema, doc.frontmatter, { throwOnError: true });
```

## Features

- Markdown + frontmatter parsing
- Standard Schema compatibility
- Zod-based schema authoring
- Helpful error formatting
- Fast validation for large content sets

## Documentation

https://docs.matthewhendricks.net/fieldtest/

## License

MIT
npm package: @fieldtest/openapi
Description: OpenAPI helpers for FieldTest (OpenAPI -> Zod).
Author: Matthew Hendricks
Latest version: 1.0.2

# @fieldtest/openapi

Convert OpenAPI specs into Zod schemas you can validate with FieldTest.

## Install

```bash
pnpm add @fieldtest/openapi
```

## Usage

```ts
import { loadOpenApiSchemas } from "@fieldtest/openapi";
import { validate } from "@fieldtest/validation-lib";

const { components, paths } = loadOpenApiSchemas("./openapi.yaml");

const UserSchema = components.User;
const [ok, result] = validate(UserSchema, { id: "123" });
```

## Path schemas

The registry includes request/response schemas when possible:

```ts
const registry = loadOpenApiSchemas("./openapi.yaml");
const createUser = registry.paths["/users"].post;

const bodySchema = createUser.requestBody;
const responseSchema = createUser.responses["201"];
```

## Notes

- Supports common OpenAPI schema features: `$ref`, `enum`, `oneOf`, `anyOf`, `allOf`, `nullable`, object/array types.
- Only resolves local `#/components/schemas/*` refs.
- Parses JSON or YAML OpenAPI files.
npm package: @fieldtest/registry
Description: Schema registry for FieldTest SDK
Author: Matthew Hendricks
Latest version: 1.0.2


# Fieldtest Registry

The Fieldtest Registry is a collection of schemas for common content types.

## Running the Standard Schema Example

To run the Standard Schema example in this package, use the following commands from this directory:

```powershell
# Compile the example to CommonJS JavaScript
tsc standard-schema.example.ts --module commonjs --esModuleInterop --outDir dist

# Run the compiled JavaScript with Node.js
node dist/standard-schema.example.js
```

You should see output like:

```json
Success: hello world
Expected failure: Error: [
  {
    "message": "Must be a string"
  }
]
```

> Note: Directly running the example with ts-node may fail due to ESM/CommonJS module system conflicts. Compiling first is the most reliable approach.

## Running All Examples Easily

To run all Standard Schema example files and see a summary of results, use:

```powershell
# Compile the runner script and run it
# (from this directory)
tsc run-examples.ts --module commonjs --esModuleInterop --outDir dist
node dist/run-examples.js
```

You'll see colorized output for each example and a summary at the end, e.g.:

```log
[SUCCESS] standard-schema.example.ts
[SUCCESS] standard-schema-async.example.ts
[SUCCESS] standard-schema-missing-types.example.ts
[SUCCESS] standard-schema-bad-result.example.ts

Summary: 4 passed, 0 failed
```

> This is the easiest way to check all example behaviors at once!
npm package: @fieldtest/validation-lib
Description: Reusable TypeScript validation library using Zod schemas
Author: Matthew Hendricks
Latest version: 1.0.2

# @fieldtest/validation-lib

A TypeScript validation library that works with both Astro and Next.js applications, building on top of Zod and integrated with @docs-score/core.

## Features

- **Framework Agnostic**: Works with both Astro and Next.js
- **Zod Integration**: Built on top of Zod for powerful schema validation
- **@docs-score/core Integration**: Leverages existing validation from @docs-score/core
- **CLI Interface**: Command-line tools for validation
- **Common Schemas**: Pre-built schemas for common validation needs
- **Type Safety**: Full TypeScript support with inferred types

## Installation

```bash
# If you're in the monorepo
pnpm add @fieldtest/validation-lib

# If you're outside the monorepo
npm install @fieldtest/validation-lib
```

## Usage

### Basic Validation

```typescript
import { validate, z } from '@fieldtest/validation-lib';

const schema = z.object({
  name: z.string().min(2),
  email: z.string().email(),
  age: z.number().min(18)
});

const userData = {
  name: "Alice",
  email: "alice@example.com",
  age: 25
};

const [isValid, result] = validate(schema, userData);

if (isValid) {
  console.log("Valid data:", result);
} else {
  console.error("Invalid data:", result.errors);
}
```

### Using Pre-defined Schemas

```typescript
import { validate, DocumentSchema } from '@fieldtest/validation-lib';

const document = {
  title: "Getting Started",
  url: "https://example.com/docs/getting-started",
  headings: [
    { level: 1, text: "Getting Started" },
    { level: 2, text: "Installation" }
  ]
};

const [isValid, result] = validate(DocumentSchema, document);

if (!isValid) {
  console.error("Invalid document structure");
}
```

### Integration with @docs-score/core

```typescript
import { scanSite } from '@docs-score/core';
import { validate, ScanOptionsSchema } from '@fieldtest/validation-lib';

const options = {
  entry: "https://example.com",
  maxDepth: 3,
  concurrency: 5
};

const [isValid, validatedOptions] = validate(ScanOptionsSchema, options);

if (isValid) {
  const results = await scanSite(validatedOptions);
  console.log(`Scanned ${results.pages.length} pages`);
}
```

### CLI Usage

```bash
# Validate a URL
npx validate url https://example.com --depth 3 --concurrency 5 --output results.json

# Validate a configuration file
npx validate config ./config.json --schema ValidationConfig
```

## API Reference

### Core Functions

- `validate<T>(schema: z.ZodType<T>, input: unknown): [boolean, T | z.ZodError]`
- `validateAsync<T>(schema: z.ZodType<T>, input: unknown): Promise<[boolean, T | z.ZodError]>`
- `formatZodError(error: z.ZodError): string`

### Pre-defined Schemas

- `URLSchema`: Validates URLs
- `EmailSchema`: Validates email addresses
- `DocumentSchema`: Validates document structure
- `ValidationConfigSchema`: Validates configuration files
- `ScanOptionsSchema`: Validates @docs-score/core scan options

## License

MIT
npm package: @fieldwork/eslint-config-fieldwork
Description: ESLint config for Fieldwork projects
Author: Fieldwork
Latest version: 1.6.0

# @fieldwork/eslint-config-fieldwork

This package uses [eslint-config-airbnb](https://github.com/airbnb/javascript/tree/master/packages/eslint-config-airbnb) as a base and extends it with [Fieldwork specific rule variations](https://github.com/EMT/eslint-config-fieldwork/blob/master/rules/fieldwork.js).

## Usage

Install with peer dependencies:
```
npx install-peerdeps --dev @fieldwork/eslint-config-fieldwork
```

In `.eslintrc`:

```
{
    "extends": "@fieldwork/eslint-config-fieldwork"
}
```
npm package: @fieldwork/react-router-redux-auth
Description: React Router routes that redirect based on whether a user is logged in using @fieldwork/redux-auth
Author: Fieldwork
Latest version: 2.2.0

# @fieldwork/react-router-redux-auth

React Router routes that redirect based on whether a user is logged in using [@fieldwork/redux-auth](https://www.npmjs.com/package/@fieldwork/redux-auth).

## API

### `RedirectUnauthenticated`

Redirect an unauthenticated user if `auth.hasFailed` is `true`.

#### Props

##### `component`

A react component to render if the user is authenticated.

##### `redirectTo` (string)

The URL to redirect to if the user is not authenticated.

```
<RedirectUnauthenticated
    path="/my-dashboard"
    component={ MyDashboard }
    redirectTo="/login"
/>
```

### `RedirectAuthenticated`

Redirect an unauthenticated user if `auth.hasSucceeded` is `true`.

#### Props

##### `component`

A react component to render if the user is not authenticated.

##### `redirectTo` (string or function)

The URL to redirect to if the user is authenticated, or a function taking the authenticated user (from `auth.user`) and retuning a URL. Eg:

```
( user, redirectUrl ) => `/users/${ user.id }/dashboard`
```

##### `ignoreStateLocation` (boolean, default: `false`)

If true, the location stored in React Router’s state is ignored. See below.

#### Determining the redirect URL

When the user is authenticated, the URL they’re redirected to is the first of:

- the value of `location.state.from.pathname`
- the value

Setting `ignoreStateLocation` to `true` forces the use of the `redirectTo` prop even when there’s a value in `location.state.from.pathname`.

```
<RedirectAuthenticated
    path="/login"
    component={ LoginPage }
    redirectTo="/my-dashboard"
/>
```

### @fieldwork/redux-auth

This package also exposes `authReducer` and `withAuth` from [@fieldwork/redux-auth](https://www.npmjs.com/package/@fieldwork/redux-auth).
npm package: @fieldwork/redux-auth
Description: Auth management actions and reducer for Redux and React.
Author: Fieldwork
Latest version: 2.3.0

# @fieldwork/redux-auth

Auth management actions and reducer for Redux and React.

## API

### `authReducer`

Include auth reducers in the root reducer with:

```
import { combineReducers } from 'redux'
import { authReducer } from '@fieldwork/redux-auth'

const appReducer = combineReducers( {
    auth: authReducer,
    ...myOtherReducers,
} )
```

### `withAuth( MyComponent )`

Shorthand for:

```
import { connect } from 'react-redux'
import { authActions } from '@fieldwork/redux-auth'

const mapStateToProps = ( state ) => ( {
    auth: state.auth,
} )

connect( mapStateToProps, authActions )( MyComponent )
```

### Action Creators

A component connected using `withAuth` has the following actions available as props:

```
authSetWaiting()
authSetFailed()
authSetSucceeded( {
    id: null | number | string,
    user: { [key: string]: any },
} )
```

### `auth` Prop

A component connected using `withAuth` has an `auth` prop containing the following state:

```
{
    id: null | number | string,
    user: {},
    isWaiting: null | boolean,
    isDone: boolean,
    hasFailed: null | boolean,
    hasSucceeded: null | boolean,
}
```

Default state:

```
{
    id: null,
    user: {},
    isWaiting: null,
    isDone: false,
    hasFailed: null,
    hasSucceeded: null,
}
```

Example states:

```
authSetWaiting()

{
    ...currentState,
    isWaiting: true,
    isDone: false,
}

authSetFailed()

{
    user: {},
    id: null,
    isWaiting: false,
    isDone: true,
    hasFailed: true,
    hasSucceeded: false,
}

authSetSucceeded( {
    id: 123,
    user: {
        id: 123,
        firstName: 'Bob',
        email: 'bob@example.com',
    }
} )

{
    user: {
        id: 123,
        firstName: 'Bob',
        email: 'bob@example.com',
    },
    id: 123,
    isWaiting: false,
    isDone: true,
    hasFailed: false,
    hasSucceeded: true,
}
```
npm package: @fiercecat/payload-plugin-oidc
Description: OIDC plugin for Payload 2.0
Author: Yix Huang
Latest version: 1.46.0

# OIDC plugin for Payload CMS

<a href="LICENSE">
  <img src="https://img.shields.io/badge/license-MIT-brightgreen.svg" alt="Software License" />
</a>
<a href="https://github.com/gousta/payload-plugin-oidc/issues">
  <img src="https://img.shields.io/github/issues/gousta/payload-plugin-oidc.svg" alt="Issues" />
</a>
<a href="https://npmjs.org/package/payload-plugin-oidc">
  <img src="https://img.shields.io/npm/v/payload-plugin-oidc.svg?style=flat-squar" alt="NPM" />
</a>

## Features

- Adds ability to sign in with your own OIDC provider
- Adds sign in button on login page
- Supports sign in and optional creation of user

## Installation

```
npm install payload-plugin-oidc
# or
yarn add payload-plugin-oidc
```

## Usage

```js
// payload.config.ts
import { oidcPlugin } from 'payload-plugin-oidc';

export default buildConfig({
  serverURL: process.env.SERVER_URL,
  collections: [Users],
  plugins: [
    oidcPlugin({
      clientID: process.env.OIDC_CLIENT_ID,
      clientSecret: process.env.OIDC_CLIENT_SECRET,
      authorizationURL: `${process.env.OIDC_URI}/oidc/auth`,
      tokenURL: `${process.env.OIDC_URI}/oidc/token`,
      initPath: `/oidc/signin`,
      callbackPath: `/oidc/callback`,
      callbackURL: `${process.env.SELF_URL}/oidc/callback`,
      redirectUriCookieName: `42kit_connect_redirect_url`,
      connectPath: `/oidc/connect`,
      scope: 'openid offline_access profile email custom_data',
      mongoUrl: process.env.DATABASE_URI,
      components: {
        Button: SignInButton, //can be your own custom component
        position: "beforeLogin" //beforeLogin | afterLogin
      },
      userCollection: {
        slug: Users.slug,
        searchKey: 'email',
      },
      registerUserIfNotFound: true,
      async userinfo(accessToken) {
        const { data: user } = await axios.get(`${process.env.OIDC_URI}/oidc/me`, {
          headers: {
            Authorization: `Bearer ${accessToken}`,
          },
        });

        return {
          sub: user.sub,
          name: user.name,
          email: user.email,
          // You can use OIDC user custom data to get the role for this app
          role: user.custom_data?.my_app_role,

          // or you can do something like this
          // role: user.custom_data?.role ? 'admin' : 'editor',
        };
      },
    }),
  ],
});
```

## Contributing

Contributions and feedback are very welcome.

To get it running:

1. Clone the project.
2. `npm install`
3. `npm run build`

## License

The MIT License (MIT). Please see [License File](LICENSE) for more information.

[link-contributors]: ../../contributors
npm package: @fieron/ultraviolet-web-proxy
Description: Highly sophisticated proxy used for evading internet censorship or accessing websites in a controlled sandbox using the power of service-workers and more!
Latest version: 3.2.12

<p align="center"><img src="https://raw.githubusercontent.com/titaniumnetwork-dev/Ultraviolet-Static/main/public/uv.png" height="250"></p>

<h1 align="center">Ultraviolet</h1>

<a href="https://www.npmjs.com/package/@titaniumnetwork-dev/ultraviolet"><img src="https://img.shields.io/npm/v/@titaniumnetwork-dev/ultraviolet.svg?maxAge=3600" alt="npm version" /></a>

Ultraviolet is a highly advanced web proxy used for evading internet censorship or accessing websites in a controlled sandbox. It is designed with security and performance in mind. Ultraviolet intercepts HTTP requests with a service worker, while adhering to the [TompHTTP specifications](https://github.com/tomphttp) and is a leader in innovative web proxy technologies.

## Features

Ultraviolet offers several features that set it apart from its predecessors, including CAPTCHA and hCAPTCHA support, URL encoding settings for added security, client-side configuration via service-workers, high speed compared to other web proxies, blacklist settings and more for easy hosting, leak prevention, regular updates, and improved resource usage and speed for better setups with a dedicated server instance.

## Supported Sites

Some of the popular websites that Ultraviolet supports include:

- [Google](https://google.com)
- [Youtube](https://www.youtube.com)
- [Spotify](https://spotify.com)
- [Discord](https://discord.com)
- [Reddit](https://reddit.com)
- [GeForce NOW](https://play.geforcenow.com/)
- [now.gg](https://now.gg)

## Used by

- [Holy Unblocker LTS](https://github.com/QuiteAFancyEmerald/Holy-Unblocker)
- [Alu](https://github.com/titaniumnetwork-dev/Alu)
- [Incognito](https://github.com/titaniumnetwork-dev/Incognito)
- [Nebula](https://github.com/NebulaServices/Nebula)
- [AnuraOS](https://github.com/MercuryWorkshop/anuraOS)
- [Terbium](https://github.com/TerbiumOS/webOS)
- [Metallic](https://github.com/Metallic-Web/Metallic)

## Upgrading

A guide for updating from any version to v3 can be found [here](https://github.com/titaniumnetwork-dev/Ultraviolet/wiki/Upgrading).

## Older Ultraviolet versions

Starting from v3, Ultraviolet uses [bare-mux](https://github.com/MercuryWorkshop/bare-mux), a library that allows you to switch out your Bare client.

If you operate using an older Ultraviolet, we encourage you to update.

If you're too lazy to do either of the above, you can install an outdated and unsupported version of Ultraviolet.

```sh
npm install @titaniumnetwork-dev/ultraviolet@1
```

## Changelog

Changes are documented in the [changelog](./CHANGELOG.md).

## Deployment

This repository can be built, but it can't be deployed to any services. See [Ultraviolet-App](https://github.com/titaniumnetwork-dev/Ultraviolet-App) for a complete and customizable Ultraviolet setup that you can deploy.

## Documentation

Documentation can be found in the [wiki](https://github.com/titaniumnetwork-dev/Ultraviolet/wiki).
npm package: @fieron/web-proxy-toolbar
Description: This template should help get you started developing with Vue 3 in Vite.
Latest version: 0.2.15

# web-proxy-toolbar

This template should help get you started developing with Vue 3 in Vite.

## Recommended IDE Setup

[VSCode](https://code.visualstudio.com/) + [Volar](https://marketplace.visualstudio.com/items?itemName=Vue.volar) (and disable Vetur) + [TypeScript Vue Plugin (Volar)](https://marketplace.visualstudio.com/items?itemName=Vue.vscode-typescript-vue-plugin).

## Type Support for `.vue` Imports in TS

TypeScript cannot handle type information for `.vue` imports by default, so we replace the `tsc` CLI with `vue-tsc` for type checking. In editors, we need [TypeScript Vue Plugin (Volar)](https://marketplace.visualstudio.com/items?itemName=Vue.vscode-typescript-vue-plugin) to make the TypeScript language service aware of `.vue` types.

If the standalone TypeScript plugin doesn't feel fast enough to you, Volar has also implemented a [Take Over Mode](https://github.com/johnsoncodehk/volar/discussions/471#discussioncomment-1361669) that is more performant. You can enable it by the following steps:

1. Disable the built-in TypeScript Extension
    1) Run `Extensions: Show Built-in Extensions` from VSCode's command palette
    2) Find `TypeScript and JavaScript Language Features`, right click and select `Disable (Workspace)`
2. Reload the VSCode window by running `Developer: Reload Window` from the command palette.

## Customize configuration

See [Vite Configuration Reference](https://vitejs.dev/config/).

## Project Setup

```sh
npm install
```

### Compile and Hot-Reload for Development

```sh
npm run dev
```

### Type-Check, Compile and Minify for Production

```sh
npm run build
```

### Lint with [ESLint](https://eslint.org/)

```sh
npm run lint
```