open-index/open-npm huggingface dataset:
npm package: @okty/okai-mcp
Description: Local stdio MCP server for okai-mcp
Latest version: 0.1.0

# @okty/okai-mcp

`@okty/okai-mcp` 是 `okai-mcp` 的本地 `stdio` MCP Server。

它提供一个 MCP 工具：

- `analyze_image`
  - 需要分析、描述或从图片中提取信息时使用
  - 支持 `HTTP/HTTPS URL` 或本地文件路径
  - 如果本地路径以 `@` 开头，传入前先去掉 `@`
  - 示例：
    - `https://example.com/image.jpg`
    - `images/photo.png`
    - `/Users/username/Documents/image.jpg`
  - 仅支持 `JPEG`、`PNG`、`WebP`
  - 本地进程读取图片后转成 `base64`
  - 再调用远程业务服务完成图片理解

## 环境变量

- `OKAI_API_HOST`：远程服务地址，例如 `http://127.0.0.1:8080`
- `OKAI_API_KEY`：远程服务 API Key

## 本地开发

```bash
npm install
npm run build
node dist/index.js
```

## 打包检查

发布前先确认 npm 包内容：

```bash
npm run pack:check
```

## 发布到 npm

首次发布前，建议先确认你已登录到拥有 `@okty` scope 发布权限的 npm 账号。

```bash
npm publish
```

如果是 scoped public package：

```bash
npm publish --access public
```

## 加入 Claude Code

发布后，其他用户不需要再写本地文件路径，可以直接用 `npx`：

```bash
claude mcp add okai-mcp \
  --scope user \
  --env OKAI_API_HOST=http://127.0.0.1:8080 \
  --env OKAI_API_KEY=replace-with-your-api-key \
  -- npx -y @okty/okai-mcp
```

如果用户已经全局安装：

```bash
npm install -g @okty/okai-mcp

claude mcp add okai-mcp \
  --scope user \
  --env OKAI_API_HOST=http://127.0.0.1:8080 \
  --env OKAI_API_KEY=replace-with-your-api-key \
  -- okai-mcp
```
npm package: @okunishinishi/react-click-outside
Description: ClickOutside component for React
Author: TJ Holowaychuk
Latest version: 1.1.1


# ClickOutside

React click outside component.

## Installation

```
$ npm install tj/react-click-outside
```

## Example

```js
<ClickOutside onClickOutside={::this.close}>
  <p>Im a menu or something that you want to hide when clicking outside.</p>
</ClickOutside>
```

## Badges

![](https://img.shields.io/badge/license-MIT-blue.svg)
![](https://img.shields.io/badge/status-stable-green.svg)

---

> [tjholowaychuk.com](http://tjholowaychuk.com) &nbsp;&middot;&nbsp;
> GitHub [@tj](https://github.com/tj) &nbsp;&middot;&nbsp;
> Twitter [@tjholowaychuk](https://twitter.com/tjholowaychuk)
npm package: @okunishinishi/signal-master
Description: Simple signaling server for SimpleWebRTC
Latest version: 1.0.4

# Deprecated

The open-source version of SimpleWebRTC has been deprecated. This repository will remain as-is but is no longer actively maintained.
Read more about the "new" SimpleWebRTC (which is an entirely different thing) on https://simplewebrtc.com
# signalmaster

A simple signaling server for clients to connect and do signaling for WebRTC.

Specifically created as a default connection point for [SimpleWebRTC.js](https://github.com/HenrikJoreteg/SimpleWebRTC)

It also supports vending STUN/TURN servers with the shared secret mechanism as described in [this draft](http://tools.ietf.org/html/draft-uberti-behave-turn-rest-00).  This mechanism is implemented e.g. by [rfc-5766-turn-server](https://code.google.com/p/rfc5766-turn-server/) or by a [patched version](https://github.com/otalk/restund) of [restund](http://creytiv.com/restund.html).

Read more:
 - [Introducing SimpleWebRTC and conversat.io](http://blog.andyet.com/2013/02/22/introducing-simplewebrtcjs-and-conversatio/)
 - [SimpleWebRTC.com](http://simplewebrtc.com)
 - [talky.io](https://talky.io)

## Running

Running the server requires a valid installation of node.js which can be installed from the nodejs.org website. After installing the package you will need to install the node dependencies.

1) npm install

2) run the server using "node server.js"

3) In the console you will see a message which tells you where the server is running:

                        "signal master is running at: http://localhost:8888"

4) Open a web browser to the specified URL and port to ensure that the server is running properly. You should see the message when you go to the /socket.io/ subfolder (e.g. http://localhost:8888/socket.io/), you should see a message like this:

						{"code":0,"message":"Transport unknown"}

### Production Environment
* generate your ssl certs

```shell
$ ./scripts/generate-ssl-certs.sh
```
* run in Production mode

```shell
$ NODE_ENV=production node server.js
```

## Use with Express
    var express = require('express')
    var sockets = require('signalmaster/sockets')

    var app = express()
    var server = app.listen(port)
    sockets(server, config) // config is the same that server.js uses

## Docker

You can build this image by calling:  

    docker build -t signalmaster https://github.com/andyet/signalmaster.git

To run the image execute this:  

    docker run --name signalmaster -d -p 8888:8888 signalmaster

This will start a signal master server on port 8888 exposed on port 8888.
npm package: @okuryu/grok-regexp
Description: Grok patterns with native JavaScript RegExp
Author: Ryuichi Okumura
Latest version: 1.0.0-alpha.2

# grok-regexp

This is a tool that interprets the format of the Grok pattern contained in the passed string and converts it into a named capturing group through a native JavaScript regular expression.

## Usage

```sh
npm install @okuryu/grok-regexp
```

```ts
import { GrokRegExp } from "@okuryu/grok-regexp";

const pattern =
  '%{IP:client} \\[%{TIMESTAMP_ISO8601:timestamp}\\] "%{WORD:method} %{URIHOST:site}%{URIPATHPARAM:url}" %{INT:code} %{INT:request} %{INT:response} - %{NUMBER:took} \\[%{DATA:cache}\\] "%{DATA:mtag}" "%{DATA:agent}"';
const input =
  '203.35.135.165 [2016-03-15T12:42:04+11:00] "GET memz.co/cloud/" 304 962 0 - 0.003 [MISS] "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36"';

const gre = new GrokRegExp(pattern);
const result = gre.exec(input);
console.log(result?.groups);
```

```json
{
  "client": "203.35.135.165",
  "timestamp": "2016-03-15T12:42:04+11:00",
  "method": "GET",
  "site": "memz.co",
  "url": "/cloud/",
  "code": "304",
  "request": "962",
  "response": "0",
  "took": "0.003",
  "cache": "MISS",
  "mtag": "-",
  "agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36"
}
```
npm package: @okutanidaichi/moqt
Description: Media over QUIC package
Author: Okutani Daichi
Latest version: 0.7.1

# @okutanidaichi/moqt

This is a JavaScript client for Media over QUIC.
It enables JS clients to connect and communicate with the Go implementation of the Media over QUIC protocol (gomoqt).

## Installation

To install the client, use the following command:

```bash
npm install @okutanidaichi/moqt
```
npm package: @okutanihayato/analytics
Description: Analytics SDK for Emulsia Platform - Track user behavior and measure KPIs
Author: Hayato Okutani
Latest version: 0.1.0

# @emulsia/analytics

Analytics SDK for Emulsia Platform - Track user behavior and measure KPIs automatically.

## Features

- 🚀 Zero-config tracking for Next.js + Firebase apps
- 📊 Automatic collection of 7 event types
- 🔒 Privacy-first design (no sensitive data collection)
- 🎯 Built for manufacturing industry DX

## Installation

This package is part of the Emulsia Platform monorepo. To use it in the main application:

```bash
# From the root of emulsia-platform
cd packages/analytics-sdk
npm install
npm run build
```

Then in the main app's package.json, add:

```json
{
  "dependencies": {
    "@emulsia/analytics": "file:./packages/analytics-sdk"
  }
}
```

## Usage

### 1. Initialize in your Next.js app

```typescript
// src/app/layout.tsx or appropriate component
'use client';

import { useEffect } from 'react';
import { useAuth } from '@/hooks/useAuth';
import { initAnalytics } from '@emulsia/analytics';

export default function AnalyticsProvider({ children }) {
  const { user } = useAuth();

  useEffect(() => {
    if (user) {
      initAnalytics({
        projectId: process.env.NEXT_PUBLIC_FIREBASE_PROJECT_ID!,
        userId: user.uid,
        enabled: process.env.NEXT_PUBLIC_ANALYTICS_ENABLED === 'true',
      });
    }
  }, [user]);

  return children;
}
```

### 2. Add environment variable

```bash
# .env.local
NEXT_PUBLIC_ANALYTICS_ENABLED=true
```

### 3. Update Firestore rules

```javascript
// firestore.rules
match /analytics_events/{eventId} {
  allow create: if request.auth != null
    && request.resource.data.userId == request.auth.uid;

  allow read: if false;
}
```

## Tracked Events

| Event Type | Auto-collected | Description |
|------------|----------------|-------------|
| screen_view | ✅ | Page navigation |
| click | ✅ | All clicks |
| scroll | ✅ | Scroll depth (10% intervals) |
| time_spent | ✅ | Time on page |
| focus | ✅ | Input focus duration |
| keypress | ✅ | Keypress count (aggregated per 10s) |
| error | ✅ | JavaScript errors |

## Privacy

- **No sensitive data**: We don't collect keypress content, only counts
- **User consent**: Built-in consent management (auto-consent in Phase 1)
- **Anonymization**: Error messages are truncated to 500 chars

## Requirements

- Next.js 14+
- Firebase 10+
- TypeScript 5+

## License

MIT

## Author

Hayato Okutani (Emulsia)
npm package: @okuzen/jupyterlab-atom-one-light
Description: Atom One Light for JupyterLab
Author: okuzen
Latest version: 0.1.1

# Atom One Light Theme for Jupyter Lab

Inspired by [VSCode Atom One Light](https://github.com/akamud/vscode-theme-onelight) which is base on [Atom's One Light theme](https://github.com/atom/one-light-syntax).

Only test JupyterLab 3.2.8 in Chrome 79 and Edge 79.

![screenshot](./img/screenshot.png)

## Install


```shell
jupyter labextension install kuzen/jupyterlab-atom-one-light
```

or

```shell
git clone https://github.com/kuzen/jupyterlab-atom-one-light
cd jupyterlab-atom-one-light
npm install
jupyter labextension install .
```

To enable theme scrollbars:  

> Settings -> Jupyterlab Theme -> Theme Scrollbars


## Ref  

<https://github.com/jupyterlab/jupyterlab/blob/master/packages/theme-light-extension/style/variables.css>

<https://github.com/atom/one-light-ui>

<https://github.com/DavidZhang73/jupyterlab-atom-one-dark-theme>

<https://github.com/akamud/vscode-theme-onelight>

<https://code.visualstudio.com/api/references/theme-color#editor-widget-colors>
npm package: @okvoice/ui
Description: okvoice web前端公用组件库,适用于okvoice内部admin,pc端。此组件针对element-ui进行了二次封装
Author: renlin@okvoice.com
Latest version: 0.1.8

# ok-components

## Project publish

```
1. 安装源管理
npm install -g nrm 
2. 新建源
nrm add oknpm http://192.168.2.129:7001
3. 切换源
nrm use oknpm
4. 目前只有管理员可以发布组件和删除,如需新增请联系管理员添加(添加后需要重启仓库)
admin@okyuyin.com
5. 组件或者工具，开发完毕后（发布更新时需要迭代 version 版本）
npm publish
6. 删除要用force强制删除
npm --force unpublish 完整包名

```

## Project setup
```
npm install
```

### Compiles and hot-reloads for development
```
npm run serve
```

### Compiles and minifies for production
```
npm run build
```

### Lints and fixes files
```
npm run lint
```

### Customize configuration
See [Configuration Reference](https://cli.vuejs.org/config/).