open-index/open-npm huggingface dataset:
npm package: @oopsy/vuepress-plugin-external-sidebar
Description: Vuepress plugin to enable separate sidebar config files
Author: oopsy
Latest version: 1.0.3

# Vuepress Plugin External Sidebar

In my opinion, config of TOC should be placed along with
the `doc` directory, rather than in `config.js`. e.g.,
assume the directory
```
.
|--- docs
|    |--- .vuepress
|    |
|    |--- guide
|    |    |--- README.md
|    |    |--- next.md
|    |    |--- toc.js
|    |
|    |--- api
|         |--- README.md
|         |--- details.md
|         |--- toc.js
|     
|---- package.json
```
where `toc.js` in each dir contains the content of dir configuration.
e.g.
```js
// docs/guide/toc.js
module.exports = [
  '', 'next'
]
```

Then this plugin will automatically inject the sidebar prop into
`themeConfig`, and if there is no `toc.js` then `auto` field is applied.
npm package: @oorestisime/quarry
Description: Experimental ClickHouse-native query builder for TypeScript.
Latest version: 0.2.0

<p align="center">
  <img src="./.github/assets/logo.png" width="120" alt="Quarry logo" />
</p>

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

<p align="center">
  <a href="https://www.npmjs.com/package/@oorestisime/quarry"><img src="https://img.shields.io/npm/v/%40oorestisime%2Fquarry" alt="npm version" /></a>
</p>

Experimental ClickHouse-native query builder for TypeScript.

Quarry is a query builder first. It is not trying to be an ORM or hide ClickHouse behind a generic multi-dialect SQL abstraction.

## Docs

Public docs are available at [ch-quarry.vercel.app](https://ch-quarry.vercel.app).

The docs source lives in [`docs/`](./docs) and is built with
[Fumadocs](https://fumadocs.dev). To run it locally:

```bash
cd docs
pnpm install
pnpm dev
```

The site will be available on http://localhost:3000.

Highlights:

- [Approach](https://ch-quarry.vercel.app/docs/concepts/approach) &mdash; what Quarry is and is not
- [Getting started](https://ch-quarry.vercel.app/docs/guides/getting-started) &mdash; install and run your first query
- [Inserts](https://ch-quarry.vercel.app/docs/guides/inserts) &mdash; value inserts and `INSERT INTO ... SELECT`
- [Roadmap](https://ch-quarry.vercel.app/docs/roadmap) &mdash; what is likely to land next

## Status

This package is still in the early alpha stage. The current API is already validated against a real ClickHouse instance in integration tests, but the surface may still change before a stable release.

## Current Scope

- typed selects and inserts, including `INSERT INTO ... SELECT`
- joins, subqueries, and CTEs
- `FINAL`, `PREWHERE`, `GROUP BY`, and `HAVING`
- `toSQL()` and `execute()`

See the [docs site](https://ch-quarry.vercel.app) for the full supported API, runtime semantics, and concept guides.

## Example

```ts
const rows = await db
  .selectFrom("event_logs as e")
  .select("e.user_id", "e.event_type")
  .where("e.event_type", "=", "signup")
  .orderBy("e.created_at", "desc")
  .limit(50)
  .execute()
```

## Naming

The project name is Quarry. The npm package name is `@oorestisime/quarry`.
npm package: @oosawy/react-warp
Description: Construct Warp Tunnels in React
Latest version: 0.0.2

# react-warp

Construct Warp Tunnels to warp elements between renders in React🪐

> **Warning**
> This library is still Proof of Concept, and not tested enough. Don't use this in production!

## Motivation

An article is work in progress.

## Install

```sh
npm i @oosawy/react-warp
```

## Usage

1. Add `<WarpProvider />` your app to prepare the warp tunnels.

```tsx
// if you use next.js, _app.tsx is good place to put WarpProvider
import type { AppProps } from 'next/app'
import { WarpProvider } from '@oosawy/react-warp'

export default function MyApp({ Component, pageProps }: AppProps) {
  return (
    <WarpProvider>
      <Component {...pageProps} />
    </WarpProvider>
  )
}
```

2. Then wrap the element which you want to be warped with `<Warp />`. then the element will be warped to the same `<Warp />` in other renders.
   Note: the children are only allowed to have one React element, which must have a `key` prop.

```tsx
const IndexPage = () => {
  return (
    <div>
      <LandingLayout
        header={
          <Warp>
            <input type="text" key="search-input" />
          </Warp>
        }
      >
        <h1>The search input warps when you navigate to another page!</h1>
        <p>So the text you entered will persist even though its state is not managed.</p>
      </LandingLayout>
    </div>
  )
}

const SearchPage = () => {
  return (
    <div>
      <SearchLayout>
        <Warp>
          <input type="text" key="search-input" />
        </Warp>
      </SearchLayout>
    </div>
  )
}
```
npm package: @oosmetrics/mcp
Description: oosmetrics MCP server - search repos, compare metrics, discover alternatives across 330K+ GitHub projects
Latest version: 1.0.2

# @oosmetrics/mcp

MCP server for [oosmetrics](https://oosmetrics.com) - search, compare, and analyze 330,000+ open-source GitHub repos by growth rate, acceleration, and originality.

Works with any MCP-compatible client: Claude Code, Cursor, Windsurf, and others.

## Install

```bash
npx @oosmetrics/mcp
```

Or add to your MCP client settings:

```json
{
  "mcpServers": {
    "oosmetrics": {
      "command": "npx",
      "args": ["@oosmetrics/mcp"],
      "env": {
        "OOSMETRICS_API_KEY": "oosm_your_key_here"
      }
    }
  }
}
```

Get your API key at [oosmetrics.com/profile](https://oosmetrics.com/profile) (Pro or AI tier required).

## Tools

Available tools depend on your subscription tier. The server fetches the filtered tool list from the oosmetrics API at startup.

### Pro + AI tier (7 tools)

- **search** - Find repos by natural language query, language, or sort criteria
- **get_repo** - Get detailed metrics, grades, and description for a repo
- **compare** - Compare 2-5 repos side by side
- **trending** - Get trending repos, optionally filtered by language
- **alternatives** - Find similar repos using embedding similarity
- **history** - Get historical metrics time series
- **analyze** - AI-powered deep analysis of any repo

### AI tier only (3 additional tools)

- **existence_check** - Check if a project idea already exists
- **dependency_discovery** - Find libraries to help achieve a goal
- **license_check** - Check dependency licenses for conflicts

## How it works

The MCP server communicates with your client over stdio (standard input/output). It makes HTTPS requests only to `api.oosmetrics.com` using your API key. No local ports opened, no background processes, no telemetry.

Source code: [github.com/AlessandroFlati/GitHubMetrics/tree/main/mcp](https://github.com/AlessandroFlati/GitHubMetrics/tree/main/mcp)

## License

MIT
npm package: @oosmetrics/openclaw-plugin
Description: oosmetrics plugin for OpenClaw - search, compare, and analyze 330K+ GitHub repos
Latest version: 1.0.8

# @oosmetrics/openclaw-plugin

OpenClaw plugin for [oosmetrics](https://oosmetrics.com) - search, compare, and analyze 330,000+ open-source GitHub repos by growth rate, acceleration, and originality.

## Install

```bash
openclaw plugins install @oosmetrics/openclaw-plugin
```

## Configure

Add your API key to your OpenClaw settings:

```json
{
  "plugins": {
    "entries": {
      "oosmetrics": {
        "enabled": true,
        "config": {
          "apiKey": "oosm_your_key_here"
        }
      }
    }
  }
}
```

Get your API key at [oosmetrics.com/profile](https://oosmetrics.com/profile) (Pro or AI tier required).

## Tools

The plugin registers native tools in your OpenClaw agent. Available tools depend on your subscription tier.

### Pro + AI tier (7 tools)

- **oosmetrics_search** - Find repos by natural language query, language, or sort criteria
- **oosmetrics_get_repo** - Get detailed metrics, grades, and description for a repo
- **oosmetrics_compare** - Compare 2-5 repos side by side
- **oosmetrics_trending** - Get trending repos, optionally filtered by language
- **oosmetrics_alternatives** - Find similar repos using embedding similarity
- **oosmetrics_history** - Get historical metrics time series
- **oosmetrics_analyze** - AI-powered deep analysis of any repo

### AI tier only (3 additional tools)

- **oosmetrics_existence_check** - Check if a project idea already exists
- **oosmetrics_dependency_discovery** - Find libraries to help achieve a goal
- **oosmetrics_license_check** - Check dependency licenses for conflicts

## How it works

The plugin makes HTTPS requests to `api.oosmetrics.com` using your API key. No local servers, no background processes, no ports opened. All data flows through the oosmetrics REST API and MCP endpoint.

Source code: [github.com/AlessandroFlati/GitHubMetrics/tree/main/openclaw-plugin](https://github.com/AlessandroFlati/GitHubMetrics/tree/main/openclaw-plugin)

## License

MIT