open-index/open-npm huggingface dataset:
npm package: @orbisclub/modules
Description: Decentralized social modules created with the Orbis SDK
Author: OrbisWeb3
Latest version: 0.0.43

# @orbisclub/modules

> Decentralized social modules created with the Orbis SDK

[![NPM](https://img.shields.io/npm/v/@orbisclub/modules.svg)](https://www.npmjs.com/package/@orbisclub/modules) [![JavaScript Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://standardjs.com)

## Install

```bash
npm install --save @orbisclub/modules
```

## Usage

```jsx
import { ChatBox } from '@orbisclub/modules'
import "@orbisclub/modules/dist/index.modern.css";

function App() {
  /** The context parameter in the <ChatBox/> object must be your group or channel id or a custom string */
  return(
    <ChatBox context="kjzl6cwe1jw147b42j1yjoxyzrzeg3czq5mjm1lrmg5eeq43yutje3f2s0s2n5h" poweredByOrbis="black" />
  );
}
```

## Styling
By default, the chat box is going to follow a default orange theme but it's possible to customize it to have the chatbox follow your own style, here is how it works:

```jsx
import { ChatBox } from '@orbisclub/modules'
import "@orbisclub/modules/dist/index.modern.css";

let chat_theme = {
  /** Style for main buttons */
  mainCta: {
    background: 'linear-gradient(135deg, #FF94B4 0%, #AA6AFB 100%)'
  },

  /** Style for the connect button */
  connectBtn: {
    background: 'linear-gradient(135deg, #FF94B4 0%, #AA6AFB 100%)'
  },

  /** Style for the messages sent and received */
  messagesContainer: {
    background: '#DDD'
  },
  messageSent: {
    background: 'linear-gradient(135deg, #FF94B4 0%, #AA6AFB 100%)'
  },
  messageReceived: {
    background: '#fff'
  },

  /** Style for the header and footer (input container) */
  header: {
    background: 'linear-gradient(135deg, #FF94B4 0%, #AA6AFB 100%)',
    color: "#FFF"
  },
  footer: {
    background: "#F2F2F2"
  },

  /** Reply text */
  replyLine: {
    borderColor: "#696969"
  },
  replyText: {
    color: "#696969"
  },

  /** Input style */
  input: {
    background: "#FFF",
    borderWidth: 1,
    borderColor: "#DDD"
  }
};

function App() {
  /** The context parameter in the <ChatBox/> object must be your group or channel id or a custom string */
  return(
    <ChatBox
      context="kjzl6cwe1jw147b42j1yjoxyzrzeg3czq5mjm1lrmg5eeq43yutje3f2s0s2n5h"
      theme={chat_theme}
      title="You can use a custom title"
      poweredByOrbis="white" />
  );
}
```

## License

MIT © [OrbisWeb3](https://github.com/OrbisWeb3)
npm package: @orbisk/vue-use-media-recorder
Description: 🪝 Vue Composable around MediaRecorder API
Author: Robin Kehl
Latest version: 0.0.4

# 🪝 vue-use-media-recorder

A Vue Composable for the MediaRecorder API

## Features

- 🎥 Record audio and video streams
- 📦 Auto import for Nuxt
- 🎨 TypeScript support
- 📚 [Documentation](https://orbisk.github.io/vue-use-media-recorder/)

## Installation

```bash
pnpm add -D @orbisk/vue-use-media-recorder
```

### Nuxt

Auto import for Nuxt is supported. Just add the module to your `nuxt.config`:

```ts
export default defineNuxtConfig({
  modules: ['@orbisk/vue-use-media-recorder/nuxt']
})
```

## Commands

Build the package:

```bash
pnpm build
```

Run the development environment (vite):

```bash
pnpm dev
```

Run the docs:

```bash
pnpm dev:docs
```

Build the docs:

```bash
pnpm build:docs
```

Lint the package:

```bash
pnpm lint
```

Run test suite:

```bash
pnpm test
```

Start Nuxt dev environment:

```bash
pnpm dev:nuxt
```

Build Nuxt environment:

```bash
pnpm build:nuxt
```

Preview Nuxt environment:

```bash
pnpm start:nuxt
```
npm package: @orbit-foundation/satellite-one
Description: First ORBIT Satellite project.
Author: ORBIT Foundation
Latest version: 0.1.1

# Satellite ONE
_Part of the ORBIT Foundation's Satellite project._

This plays no function, but serves as an analytics probe. Inside, you will find our logo, an HTML page and our `package.json` file.

(c) 2020 by the ORBIT Foundation
npm package: @orbit-js/nextjs
Description: Orbit SDK middleware for Next.js applications
Author: Orbit Team
Latest version: 1.0.10

# @orbit-js/nextjs

Orbit SDK middleware for Next.js applications with auto-instrumentation.

## Installation

```bash
npm install @orbit-js/sdk @orbit-js/nextjs
# or
yarn add @orbit-js/sdk @orbit-js/nextjs
```

## Quick Start

### 1. Create middleware.ts

Create a `middleware.ts` file in the root of your Next.js project:

```typescript
import { createOrbitMiddleware } from '@orbit-js/nextjs';

export default createOrbitMiddleware(process.env.ORBIT_API_KEY!);

export const config = {
  matcher: '/api/:path*',
};
```

### 2. Add Environment Variables

Add these required variables to `.env.local`:

```env
# Required - Your Orbit API credentials
ORBIT_API_KEY=your_api_key_here
ORBIT_API_URL=https://orbit.vercel.app

# Optional - Enable debug logs
ORBIT_DEBUG=false
```

### 3. (Optional) Enable Instrumentation

Create an `instrumentation.ts` file in the root of your project:

```typescript
export async function register() {
  if (process.env.NEXT_RUNTIME === 'nodejs') {
    await import('@orbit-js/nextjs/instrumentation');
  }
}
```

## What Gets Tracked Automatically

- ✅ API calls count
- ✅ Request latency
- ✅ Errors and exceptions
- ✅ Memory usage (with instrumentation)
- ✅ Server uptime (with instrumentation)

## Advanced Configuration

```typescript
import { createOrbitMiddleware } from '@orbit-js/nextjs';

export default createOrbitMiddleware({
  apiKey: process.env.ORBIT_API_KEY!,
  debug: true,
  ignorePaths: [/^\/_next/, /^\/static/],
  captureHeaders: true,
});
```

## Manual Tracking

You can also track custom events manually:

```typescript
import { getOrbitClient } from '@orbit-js/nextjs';

export async function POST(request: Request) {
  const orbit = getOrbitClient();
  
  orbit?.event('user_created', {
    plan: 'premium',
  });
  
  // your code
}
```

## Environment Variables

- `ORBIT_API_KEY` - Your Orbit API key (required)
- `ORBIT_API_URL` - Orbit API URL where events are sent (required, default: `https://orbit.vercel.app`)
- `ORBIT_DEBUG` - Enable debug logs (optional, default: `false`)

## Requirements

- Next.js 13.0.0 or higher
- Node.js 18.0.0 or higher

## License

MIT © Orbit Team
npm package: @orbit-logistics/notion-mcp-server
Description: MCP server for Notion integration
Author: Jan Czekala
Latest version: 0.1.0

# @orbit-logistics/notion-mcp-server

An MCP server that mirrors the entire Notion API SDK as a collection of tools, enabling Large Language Models (LLMs) to interact with Notion seamlessly.

## Overview

@orbit-logistics/notion-mcp-server is built on the Model Context Protocol (MCP) and exposes the full Notion API as tools that LLMs can use. This allows for operations such as reading, creating, updating, and deleting Notion pages directly through natural language instructions.

## Notion Integration Setup

Before using this server with Cursor or Claude Desktop, you must create a Notion integration and grant it access to your pages. Follow the instructions in the Notion documentation for creating an integration and adding the necessary permissions:

[Notion Integration Getting Started](https://developers.notion.com/docs/create-a-notion-integration#getting-started)

## Usage

### Using with Cursor

To integrate @orbit-logistics/notion-mcp-server with Cursor, follow these steps:

1. Open Cursor Settings.
2. Navigate to Features and scroll down to "MCP Servers".
3. Click on "Add new MCP server".
4. Enter a name of your choice and select "command" as the type.
5. In the command field, enter the following (replace `<notion_integration_token>` with your actual token):

```bash
npx -y @orbit-logistics/notion-mcp-server -t <notion_integration_token>
```

This command starts the server with your Notion integration token. Cursor will then use this MCP server to access Notion's API tools.

### Using with Claude Desktop

For Claude Desktop, MCP server configurations are stored in a JSON configuration file. Add the following entry to your `claude_desktop_config.json` (replace `<notion_integration_token>` with your actual token):

```json
{
  "mcpServers": {
    "notion": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-sequential-thinking-test",
        "-t",
        "<notion_integration_token>"
      ]
    }
  }
}
```

This configuration allows Claude Desktop to invoke the notion MCP server for interactions with Notion.

## License

This project is licensed under the MIT License.

## Contributing

Contributions are welcome! Please feel free to open an issue or submit a pull request with your suggestions and improvements.
npm package: @orbit-love/cli
Description: A Command Line Interface for Orbit
Author: Kevin Lewis
Latest version: 0.1.1

@orbit-love/cli
===============

[![npm version](https://badge.fury.io/js/%40orbit-love%2Fcli.svg)](https://badge.fury.io/js/%40orbit-love%2Fcli)
[![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.0-4baaaa.svg)](.github/CODE_OF_CONDUCT.md)

⚠️ An exceptionally **work-in-progress** command-line interface for interacting with your Orbit workspace. Active development on this particular project is slow as we are building features as we discover the need. Please don't use for anything serious. ⚠️

We welcome contributions! There's lots to do! Check out the [Contributing Guidelines](.github/CONTRIBUTING.md) for more information.

```sh-session
$ npx @orbit-love/cli COMMAND ARGUMENTS FLAGS
```

## Setup

### `setup`

Saves your Orbit Workspace ID and Orbit API Key. You must run this before other commands.

## Members

### `members:get OR members:find`

Shows information from a single member in your workspace. Can also display activities and notes with flags.

```
USAGE
  $ npx @orbit-love/cli members:get source value
  $ npx @orbit-love/cli members:find source value

OPTIONS
  -o, --open  opens member profile in browser
  -a, --activities  lists member's latest activities
  -n, --notes  lists member's latest notes

DESCRIPTION
Source can be any of: github, twitter, email, id
Value is a username, email, or Orbit ID
```

## Notes

### `notes:get`

Lists notes from a single member in your workspace.

```
USAGE
  $ npx @orbit-love/cli notes:get id

DESCRIPTION
id is an Orbit ID - you can get it from the URL path
```

## Activities

### `activities:get`

Lists activities, currently from a single member in your workspace only.

```
USAGE
  $ npx @orbit-love/cli activities:get

OPTIONS
  -m, --member  the member to get activities for

DESCRIPTION
id is an Orbit ID - you can get it from the URL path

EXAMPLE
npx @orbit-love/cli activities:get --member id-goes-here
```

## Supported Endpoints

The following is a list of Orbit API Endpoints and whether the CLI provides support for them:

| API   | Functionality |  Supported?
|:----------|:---------|:-------------|
| Activity Types | - |❌|
| Users | - |❌|
| Activities | <ul><li>Get a member's activities</li></ul> |🟧|
| Members | <ul><li>Get a member by ID</li><li>Find member by identity</li></ul> |🟧|
| Notes | <ul><li>Get a member's notes</li></ul> |🟧|
| Reports | - |❌|
| Reports | - |❌|
| Workspaces | - |❌|

## License

This project is under the [MIT License](./LICENSE).

## Code of Conduct

This project uses the [Contributor Code of Conduct](.github/CODE_OF_CONDUCT.md). We ask everyone to please adhere by its guidelines.