open-index/open-npm huggingface dataset:
npm package: @ooom/popcorn
Description: OOOM's core, where shared wonders live
Author: The clever devs at OOOM
Latest version: 0.8.11

<img src="https://hopskotch.s3.amazonaws.com/logos/ooom-logo-slate-on-trans.svg" style="width:400px;" />

## Popcorn (Popcore)

Popcorn (or Popcore (ha!)) is the core for OOOM. It uses `npm` and should be published to npm as it is updated.

You can create a symbolic link locally using `npm link` from within popcorn and `npm publish --access public` (soon to be private) when ready.  You will need a  OTP and a device registered with NPM to allow you to publish (typically Google Auth).

Do not publish any sensitive information within core, such-as keys, secrets etc.

Do publish constants, utils, shared functions and transformers.

### To Run

`npm install`

`npm run start`

You don't need to keep webpack running thereafter, just point at popcorn from other projects and it'll all just work.

### To Publish

`npm publish --access public` after nudging the package version.

## To Test

`npm run test`

Use `npm run test --no-config` if you don't want the logs suppressed (show console logs).

## A note about the RSA key pair

This is generated using:-

```
openssl genrsa -out private.key 4096
openssl rsa -in private.key -pubout -out public.key
```
npm package: @oooo-kit/bevm
Description: ## 概述
Author: Ted
Latest version: 0.2.1

# @oooo-kit/bevm

## 概述

@oooo-kit是一个低代码的跨链桥集成方案, 它会在业务方的网站嵌入跨链桥支付, 方便业务方接入桥服务, 降低业务方的接入成本.

@oooo-kit将会以UI组件的形式嵌入到用户的Web应用程序中

## 快速入门

### 1. 安装 @oooo-kit/bevm 库

```bash
$ pnpm install @oooo-kit/bevm
```

### 2. 初始化


#### 样式初始化

```ts
import '@oooo-kit/bevm/style.css'
```

#### OBridgeElement

```tsx
import { OBridgeElement } from '@oooo-kit/bevm'

export default () => {
	const options = {
		appId: '{{appId}}'
	}
	
	const walletAddress = '{{walletAddress}}'
	
	const provider = window.ethereum

	return <OBridgeElement walletAddress={walletAddress} provider={provider} options={options} />
}
```

#### OBridgeHistory

```tsx
import { OBridgeHistory } from '@oooo-kit/bevm'

export default () => {
	const options = {
		appId: '{{appId}}'
	}
	
	const walletAddress = '{{walletAddress}}'
	
	const provider = window.ethereum

	return <OBridgeHistory walletAddress={walletAddress} provider={provider} options={options} />
}
```

## 详细文档

### OBridgeElement

#### 时序图

![OBridgeElement](./example/assets/OBridgeElement.png)

#### API

| Prop | Description |
| --- | --- |
| walletAddress | 当前活跃的钱包地址 |
| provider | 当前活跃钱包的Ethereum Provider |
| options | OBridgeElement 配置项. https://www.notion.so/oooo-kit-bevm-SDK-abc6169a21e943779d2424b9280d4aea?pvs=21 |

**Options**

| Prop             | Description       |
| ---------------- | ----------------- |
| appId            | 指定业务方的appId |
| showMessageAlert | 指定是否使用@oooo-kit消息弹窗展示失败信息 |

**Events**

| Name | Description | Argument |
| --- | --- | --- |
| onSucceed | 用户创建交易单成功后触发 | Transaction |
| onFailed | 用户创建交易单失败后触发 | OBridgeError |

**Transaction**
| Name            | Description            |
| --------------- | ---------------------- |
| createTime      | 交易单创建时间         |
| fromChainName   | 用户发起转账的链名称   |
| fromAssetType   | 用户发起转账的资产类型 |
| fromAssetCode   | 用户发起转账的资产     |
| fromWalletAddr  | 用户发起转账钱包地址   |
| fromTxnHash     | 用户发起转账的交易hash |
| fromSwapAmount  | 用户发起转账金额       |
| fromStatus      | 用户发起转账订单状态   |
| toChainName     | 目的链名称             |
| toAssetType     | 目的资产类型           |
| toAssetCode     | 目的资产               |
| toWalletAddr    | 目的收款钱包地址       |
| toSwapAmount    | 目的收款金额           |
| toTxnHash       | 目的交易hash           |
| toStatus        | 目的订单状态           |
| binancePayOrder | Binance Pay订单信息 |

**OBridgeError**
| Name | Description    |
| ---- | -------------- |
| code | 错误码, 基于[EthersError](https://docs.ethers.org/v6/api/utils/errors/)上新增了`O_RESPONSE_ERROR`错误码管理@oooo-kit内部的接口请求错误 |
| message | 由@oooo-kit处理过的错误信息 |
| rawError | 原始的, 未被处理过的错误数据 |

### OBridgeHistory

用户交易历史列表组件, 用于展示用户通过@oooo-kit/bevm创建的交易单信息

#### 时序图

![OBridgeHistory](./example/assets/OBridgeHistory.png)

#### API

| Prop | Description |
| --- | --- |
| walletAddress | 当前活跃的钱包地址 |
| provider | 当前活跃钱包的Ethereum Provider |
| options | OBridgeHistory 配置项. https://www.notion.so/oooo-kit-bevm-SDK-abc6169a21e943779d2424b9280d4aea?pvs=21 |

**Options**

| Prop | Description |
| --- | --- |
| appId | 指定业务方的appId |

## 常见问题 (FAQ)

Q: @oooo-kit 组件嵌入形式是什么样的?

A: @oooo-kit 组件会以UI组件的形式嵌入, 组件的宽度基于容器宽度, 高度基于内容高度
npm package: @ooopsstudio/core
Description: Contracts, ports, tokens, runtime utilities, and pure helpers for the Ooops System.
Latest version: 0.1.0

# @ooopsstudio/core

Contracts, ports, tokens, runtime helpers, and pure utilities for the Ooops System.

## Install

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

## Quickstart

```ts
import {createContainer, TOK} from '@ooopsstudio/core'
import {createSystemClock} from '@ooopsstudio/core/runtime/time/system-clock'

const container = createContainer()
container.bind(TOK.Clock, createSystemClock())
```

Useful public subpaths:

- `@ooopsstudio/core/contracts/*`
- `@ooopsstudio/core/ports/*`
- `@ooopsstudio/core/runtime`
- `@ooopsstudio/core/runtime/*`
- `@ooopsstudio/core/utils`
- `@ooopsstudio/core/utils/*`
- `@ooopsstudio/core/tokens`

## Runtime Notes

- ESM-only package
- Node `>=20`
- TypeScript `>=5`
- Intended for server, worker, and tooling runtimes
- Browser-safe only for the pure contract and utility parts you explicitly bundle

## Package Policy

- Public API is defined by the package export map only
- Deep imports outside documented subpaths are unsupported
- Versioning is managed through Changesets

## License

MIT © Ooops Studio
npm package: @ooopsstudio/react
Description: Thin React adapter for the current @ooopsstudio/sdk surface.
Latest version: 0.1.0

# @ooopsstudio/react

Thin React-oriented helpers built on top of `@ooopsstudio/sdk`.

## Install

```bash
pnpm add react @ooopsstudio/react @ooopsstudio/sdk @ooopsstudio/core
# or
npm install react @ooopsstudio/react @ooopsstudio/sdk @ooopsstudio/core
```

## Quickstart

```tsx
import {instrumentFetchHandler, measurePageLoad} from '@ooopsstudio/react'

export const handler = instrumentFetchHandler(async() => {
	return new Response('ok', {status: 200})
}, {route: '/health'})

measurePageLoad({route: '/dashboard'})
```

## Runtime Notes

- ESM-only package
- Node `>=20`
- Peer dependency: `react >=18`
- Intended for React applications and build pipelines that support ESM
- Server vs browser behavior depends on the helper you import from the package root

## Package Policy

- Keep usage on the public root export only
- Versioning is managed through Changesets

## License

MIT © Ooops Studio
npm package: @ooopsstudio/sdk
Description: Framework-agnostic developer helpers built on top of @ooopsstudio/core.
Latest version: 0.1.0

# @ooopsstudio/sdk

Framework-agnostic developer helpers built on top of `@ooopsstudio/core`.

## Install

```bash
pnpm add @ooopsstudio/sdk @ooopsstudio/core
# or
npm install @ooopsstudio/sdk @ooopsstudio/core
```

## Quickstart

```ts
import {instrumentFetchHandler} from '@ooopsstudio/sdk/performance'

const handler = instrumentFetchHandler(async() => {
	return new Response('ok', {status: 200})
}, {
	route: '/health'
})
```

Useful public subpaths:

- `@ooopsstudio/sdk/performance`
- `@ooopsstudio/sdk/performance-browser`
- `@ooopsstudio/sdk/performance-db`
- `@ooopsstudio/sdk/faro-browser`
- `@ooopsstudio/sdk/events`
- `@ooopsstudio/sdk/cache`
- `@ooopsstudio/sdk/jobs`

## Runtime Notes

- ESM-only package
- Node `>=20` for server-side helpers
- Browser support depends on the subpath you import
- `performance-browser` and `faro-browser` are browser-only entrypoints

## Package Policy

- Public API is limited to the documented export map
- Prefer package subpaths over deep internal imports
- Versioning is managed through Changesets

## License

MIT © Ooops Studio
npm package: @ooopsstudio/services
Description: Runtime service implementations and cross-service bridges for the Ooops System.
Latest version: 0.1.0

# @ooopsstudio/services

Runtime service implementations and cross-service bridges for the Ooops System.

## Install

```bash
pnpm add @ooopsstudio/services @ooopsstudio/core
# or
npm install @ooopsstudio/services @ooopsstudio/core
```

## Quickstart

```ts
import {createProductionLogging} from '@ooopsstudio/services/logging/public/production'

const logger = await createProductionLogging({
	sink: {
		async write(line) {
			console.log(line)
		},
		async flush() {},
		async close() {}
	},
	context: {attributes: {service: 'example'}}
})

logger.info('service ready')
await logger.shutdown()
```

Common public families:

- `@ooopsstudio/services/logging`
- `@ooopsstudio/services/errors`
- `@ooopsstudio/services/metrics`
- `@ooopsstudio/services/tracing`
- `@ooopsstudio/services/lifecycle`
- `@ooopsstudio/services/resilience`
- `@ooopsstudio/services/performance`

Public sink helpers:

- `@ooopsstudio/services/logging/sinks`
- `@ooopsstudio/services/errors/sinks`
- `@ooopsstudio/services/metrics/sinks`
- `@ooopsstudio/services/tracing/sinks`

Bridge helpers are exported from the package root:

- `wireObservability`
- `wireLifecycleBridges`
- `wirePerformanceBridges`

## Runtime Notes

- ESM-only package
- Node `>=20`
- Intended primarily for server and worker runtimes
- Some families expose browser-safe helpers, but the package as a whole should be treated as server-first

## Export Policy

- Only the following surfaces are public:
- package root bridge and wiring helpers
- service family entrypoints such as `@ooopsstudio/services/logging`
- preset subpaths such as `@ooopsstudio/services/logging/public/production`
- sink subpaths for observability families
- Internal folders and extra helper subpaths are not part of the public npm surface

## External Sink Pattern

Observability backends are standardized at the service layer:

- `create<Service>Sink(config)`
- `resolve<Service>Sink({sink?, sinkConfig?})`
- `createNoop<Service>Sink()`

Applications should resolve env/config into `sinkConfig` and pass that into service presets instead of owning transport wiring directly.

## Versioning

Package versions are managed through Changesets. Do not edit versions manually after the initial release line is established.

## License

MIT © Ooops Studio
npm package: @ooopsstudio/svelte
Description: SvelteKit observability adapter for Ooops SDK and services.
Latest version: 0.1.0

# @ooopsstudio/svelte

SvelteKit-focused adapter for Ooops SDK and services.

## Install

```bash
pnpm add svelte @sveltejs/kit @ooopsstudio/svelte @ooopsstudio/sdk @ooopsstudio/services @ooopsstudio/core
# or
npm install svelte @sveltejs/kit @ooopsstudio/svelte @ooopsstudio/sdk @ooopsstudio/services @ooopsstudio/core
```

## Quickstart

```ts
import {createSvelteKitObservability, instrumentHandle} from '@ooopsstudio/svelte'

const observability = await createSvelteKitObservability({
	preset: 'development'
})

export const handle = instrumentHandle(
	async({event, resolve}) => await resolve(event),
	{
		performance: observability.performance,
		tracing: observability.tracing,
		logger: observability.logging
	}
)
```

## Runtime Notes

- ESM-only package
- Node `>=20`
- Peer dependencies: `svelte ^4 || ^5`, `@sveltejs/kit ^2`
- Intended for SvelteKit server and browser entrypoints that support ESM
- Package behavior is SvelteKit-oriented rather than generic Svelte-only

## Package Policy

- Use only the public root export
- Versioning is managed through Changesets

## License

MIT © Ooops Studio
npm package: @ooppstef/yupao-mcp-server
Description: yupao auto processes
Latest version: 0.1.3

# 鱼泡科技 MCP 工具集

这是成都鱼泡科技有限公司内部使用的多功能工具集（MCP），提供了与多个平台交互的能力。

## 当前支持的功能

### GitLab 集成
- ✨ MR（合并请求）评论管理
- 🔍 文件 blame 信息查询
- 🔒 内置只读模式保护
- 🌐 支持自定义 GitLab 实例

### 飞书集成
- 🔜 即将推出

## 安装

```bash
npm install @yupao/mcp
```

## 环境变量配置

### GitLab 配置
```env
GITLAB_PERSONAL_ACCESS_TOKEN=your_gitlab_token
GITLAB_API_URL=your_gitlab_instance_url
GITLAB_READ_ONLY_MODE=false  # 可选，默认为 false
```

### 飞书配置
即将推出...

## 使用示例

### GitLab 功能

#### 添加 MR 评论

```typescript
import { commentMR } from '@yupao/mcp';

// 添加评论到指定的 MR
await commentMR(
  'https://gitlab.com/your-group/your-project/-/merge_requests/123',
  '这是一条评论'
);
```

#### 获取文件 blame 信息

```typescript
import { getBlameInfo } from '@yupao/mcp';

// 获取特定文件某一行的 blame 信息
const blameInfo = await getBlameInfo(
  'your-project-id',
  'path/to/file.ts',
  42  // 行号
);
```

## 特性

- 🔗 多平台集成支持
- 📦 TypeScript 支持
- 🛡️ 错误处理机制
- 📝 详细的日志输出
- 🔒 安全保护机制

## 注意事项

- 确保已正确配置所需的环境变量
- 在只读模式下，所有写操作都将被阻止
- 建议在生产环境中使用错误处理机制
- 仅供鱼泡科技内部使用

## 维护与支持

由鱼泡科技技术团队维护，如有问题请通过内部渠道联系技术支持。

## 许可证

专有软件，仅限鱼泡科技内部使用。
npm package: @oops365/typed-object-paths
Description: Type-safe deep path access utilities for Typescript objects
Author: Oops365
Latest version: 0.1.0

# @oops365/typed-object-paths

**Type-safe deep path access utilities for TypeScript objects**

[![npm version](https://img.shields.io/npm/v/@oops365/typed-object-paths.svg)](https://www.npmjs.com/package/@oops365/typed-object-paths)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](./LICENSE)

---

## ✨ Features

- ✅ Strictly typed dot-path access (`getValue`)
- ✅ Type-safe updates (`setValue`)
- ✅ Deep path inference (`AllPaths<T>`)
- ✅ Tiny footprint, no runtime dependencies
- ✅ Written in modern TypeScript

---

## 📦 Installation

```bash
npm install @oops365/typed-object-paths
```
npm package: @oopscurity/react-spinjs
Description: A wrapper around spin.js, instantly useable
Author: Qiming Weng
Latest version: 4.0.0-rc.1

# React SpinJS

[![npm](https://img.shields.io/npm/v/react-spinjs.svg?style=flat-square)](https://www.npmjs.com/package/react-spinjs)

This is build on top of the fantastic spinner library, [spin.js](http://fgnass.github.io/spin.js/). This exposes spin.js as a component.

# Usage

```javascript
import ReactSpinner from 'react-spinjs';

// Put a default spinner
<ReactSpinner/>

// Pass in a config object
// See the documentation for spin.js
<ReactSpinner config={configObject}/>

// For convenience, pass in just a config
<ReactSpinner color="white"/>
```
npm package: @oopsie-app/node
Description: Official Oopsie backend SDK for Node.js
Latest version: 0.1.0

# @oopsie-app/node

Official Oopsie backend SDK for Node.js.

## Install

```bash
npm install @oopsie-app/node
```

## Quick start

```js
const express = require('express');
const { createOopsieNode } = require('@oopsie-app/node');

const app = express();

const oopsie = createOopsieNode({
  apiToken: process.env.OOPSIE_API_TOKEN,
  projectKey: process.env.OOPSIE_PROJECT_KEY,
  baseUrl: 'https://your-oopsie-app.com',
  releaseToken: process.env.OOPSIE_RELEASE_TOKEN,
  environment: process.env.NODE_ENV || 'production',
  release: process.env.OOPSIE_RELEASE || '1.0.0',
  framework: 'express',
});

oopsie.handshake().catch(() => {});

app.use(oopsie.expressRequestHandler());

app.get('/health', (req, res) => {
  res.json({ ok: true });
});

app.use(oopsie.expressErrorHandler());
```

## Manual capture

```js
try {
  throw new Error('Payment pipeline failed');
} catch (error) {
  await oopsie.captureException(error, {
    payload: {
      job: 'billing-sync',
    },
  });
}
```

## Release tracking

```js
await oopsie.notifyRelease({
  version: process.env.OOPSIE_RELEASE || '1.0.0',
  environment: process.env.NODE_ENV || 'production',
  commitSha: process.env.OOPSIE_COMMIT_SHA,
  description: 'Deploy production',
});
```