open-index/open-npm huggingface dataset:
npm package: @babyswap/uikit
Description: Set of UI components for pancake projects
Latest version: 0.422.69

# 🥞 Pancake UIkit

[![Version](https://img.shields.io/npm/v/@pancakeswap-libs/uikit)](https://www.npmjs.com/package/@pancakeswap-libs/uikit) [![Size](https://img.shields.io/bundlephobia/min/@pancakeswap-libs/uikit)](https://www.npmjs.com/package/@pancakeswap-libs/uikit)

Pancake UIkit is a set of React components and hooks used to build pages on Pancake's apps. It also contains a theme file for dark and light mode.

## Install

`yarn add @pancakeswap-libs/uikit`

## Setup

### Theme

Before using Pancake UIkit, you need to provide the theme file to styled-component.

```
import { ThemeProvider } from 'styled-components'
import { light, dark } from '@pancakeswap-libs/uikit'
...
<ThemeProvider theme={isDark}>...</ThemeProvider>
```

### Reset

A reset CSS is available as a global styled component.

```
import { ResetCSS } from '@pancakeswap-libs/uikit'
...
<ResetCSS />
```

### Types

This project is built with Typescript and export all the relevant types.

## How to use the UIkit

If you want to use components from the UIkit, check the [Storybook documentation](https://pancakeswap.github.io/pancake-uikit/)
npm package: @backascout/components
Description: Webcomponents created by Backa Scoutkår, for use on Kårwebben
Latest version: 0.1.0

![Built With Stencil](https://img.shields.io/badge/-Built%20With%20Stencil-16161d.svg?logo=data%3Aimage%2Fsvg%2Bxml%3Bbase64%2CPD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4KPCEtLSBHZW5lcmF0b3I6IEFkb2JlIElsbHVzdHJhdG9yIDE5LjIuMSwgU1ZHIEV4cG9ydCBQbHVnLUluIC4gU1ZHIFZlcnNpb246IDYuMDAgQnVpbGQgMCkgIC0tPgo8c3ZnIHZlcnNpb249IjEuMSIgaWQ9IkxheWVyXzEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgeG1sbnM6eGxpbms9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGxpbmsiIHg9IjBweCIgeT0iMHB4IgoJIHZpZXdCb3g9IjAgMCA1MTIgNTEyIiBzdHlsZT0iZW5hYmxlLWJhY2tncm91bmQ6bmV3IDAgMCA1MTIgNTEyOyIgeG1sOnNwYWNlPSJwcmVzZXJ2ZSI%2BCjxzdHlsZSB0eXBlPSJ0ZXh0L2NzcyI%2BCgkuc3Qwe2ZpbGw6I0ZGRkZGRjt9Cjwvc3R5bGU%2BCjxwYXRoIGNsYXNzPSJzdDAiIGQ9Ik00MjQuNywzNzMuOWMwLDM3LjYtNTUuMSw2OC42LTkyLjcsNjguNkgxODAuNGMtMzcuOSwwLTkyLjctMzAuNy05Mi43LTY4LjZ2LTMuNmgzMzYuOVYzNzMuOXoiLz4KPHBhdGggY2xhc3M9InN0MCIgZD0iTTQyNC43LDI5Mi4xSDE4MC40Yy0zNy42LDAtOTIuNy0zMS05Mi43LTY4LjZ2LTMuNkgzMzJjMzcuNiwwLDkyLjcsMzEsOTIuNyw2OC42VjI5Mi4xeiIvPgo8cGF0aCBjbGFzcz0ic3QwIiBkPSJNNDI0LjcsMTQxLjdIODcuN3YtMy42YzAtMzcuNiw1NC44LTY4LjYsOTIuNy02OC42SDMzMmMzNy45LDAsOTIuNywzMC43LDkyLjcsNjguNlYxNDEuN3oiLz4KPC9zdmc%2BCg%3D%3D&colorA=16161d&style=flat-square)

# Backa Scoutkår components

## Getting Started

```bash
yarn install
yarn start
```

To build the components for production, run:

```bash
yarn build
```

Need help? Check out our docs [here](https://stenciljs.com/docs/my-first-component).


## Naming Components

When creating new component tags, we recommend _not_ using `stencil` in the component name (ex: `<stencil-datepicker>`). This is because the generated component has little to nothing to do with Stencil; it's just a web component!

Instead, use a prefix that fits your company or any name for a group of related components. For example, all of the Ionic generated web components use the prefix `ion`.


## Using this component

There are three strategies we recommend for using web components built with Stencil.

The first step for all three of these strategies is to [publish to NPM](https://docs.npmjs.com/getting-started/publishing-npm-packages).

### Script tag

- Put a script tag similar to this `<script src='https://unpkg.com/@backascout/components@0.0.1/dist/components/components.esm.js'></script>` in the head of your index.html
- Then you can use the element anywhere in your template, JSX, html etc

### Node Modules
- Run `yarn add @backascout/components --save`
- Put a script tag similar to this `<script src='node_modules/@backascout/components/dist/components/components.esm.js'></script>` in the head of your index.html
- Then you can use the element anywhere in your template, JSX, html etc

### In a stencil-starter app
- Run `yarn add @backascout/components --save`
- Add an import to the npm packages `import '@backascout/components';`
- Then you can use the element anywhere in your template, JSX, html etc
npm package: @backbay/notary
Description: Web3 attestations, IPFS, and verification
Author: Backbay
Latest version: 0.1.0

# Notary (`@backbay/notary`)

Notary is the repo's **Web3 integration layer** for publishing and verifying "receipts":

- **IPFS uploads** (w3up / web3.storage)
- **EAS attestations** (Base / Base Sepolia)
- **Starknet wallet/session bridge** (Cartridge Controller) + signature verification

It's the bridge between "offchain proof bundles" and "onchain pointers".

## How it fits (Backbay / Cyntra)

- **Kernel → Notary (publish):** `kernel/src/cyntra/trust/notary/client.py` calls Notary to upload artifacts and mint an EAS attestation.
- **Starknet registry consumes attestations:** `packages/bb-dojo/` stores the attestation UID and can verify its existence via Herodotus proofs.
- **Clients verify receipts:** `packages/witness/` fetches and verifies attestations (Rekor/EAS/Solana) in-browser.

## Run locally

```bash
cd packages/notary

# Dev (hot)
bun run dev

# CLI (after build)
bun run build
notary --help
notary start
```

Default server: `http://localhost:7331`.

## Configuration

Notary is configured via environment variables (see `packages/notary/src/lib/config.ts`):

- `NOTARY_PORT` (default `7331`)
- `NOTARY_CHAIN` (default `base-sepolia`)
- `NOTARY_SCHEMA_UID` (EAS schema UID)
- `NOTARY_PRIVATE_KEY` (EVM key for signing transactions)
- `NOTARY_W3UP_SPACE_DID` (web3.storage space DID)
- `NOTARY_IPFS_GATEWAY` (default `https://w3s.link/ipfs/{cid}`)

Run `notary setup` / `notary status` for guided setup and sanity checks.

## HTTP Surface (high level)

- **Publish:** upload artifacts + attest receipt: `POST /publish`
- **IPFS:** `POST /upload`
- **EAS:** `POST /attest`, `GET /verify/:uid`
- **Auth:** `POST /auth/nonce`, `POST /auth/verify`
- **Identity:** `POST /identity/nonce`, `POST /identity/verify-siwe`, `GET /identity/session/:token`, `POST /identity/link`
- **Starknet:** `POST /starknet/nonce`, `POST /starknet/verify`
- **Controller:** `POST /controller/connect`, `POST /controller/execute`, `GET /controller/session/:id`

Additional experimental routes exist under `packages/notary/src/routes/` (ENS, Tableland, Lit, Bacalhau).
npm package: @backlogmd/vcs
Description: VCS abstraction for BacklogMD
Author: BacklogMD
Latest version: 0.7.0

# @backlogmd/vcs

VCS abstraction for BacklogMD: Git operations and GitHub pull request creation.

## Features

- **Git**: status, stage, commit, push, pull
- **Worktrees**: list worktrees, create worktree (with optional new branch)
- **GitHub PRs**: create a pull request (pushes the current branch, then opens a PR via the GitHub API)

Creating a PR requires a GitHub token. Set `GITHUB_TOKEN` in the environment or pass `token` in the options to `createPullRequest()`. The remote `origin` must be a GitHub URL (`https://github.com/...` or `git@github.com:...`).

## Usage

```ts
import { GitProvider, type CreatePullRequestResult } from "@backlogmd/vcs";

const git = new GitProvider("/path/to/repo");

// Stage, commit, and open a PR
await git.stageAll();
await git.commit("feat: add feature");
const result: CreatePullRequestResult = await git.createPullRequest({
  title: "feat: add feature",
  body: "Optional description",
  base: "main",
});
if (result.success && result.url) console.log("PR:", result.url);
```
npm package: @backtrace-labs/vite-plugin
Description: Backtrace Vite plugin
Author: Backtrace
Latest version: 0.0.2
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# @backtrace-labs/vite-plugin
If you're using Vite as your project bundler, you can use `@backtrace-labs/vite-plugin` to automate working with sourcemaps.

[(Source Map feature documentation)](https://docs.saucelabs.com/error-reporting/platform-integrations/source-map/)

## Enable Source Maps for Your Application

Set `sourcemap` in `output` to `true` in your `vite.config.js`:

```js
module.exports = {
  build: {
    sourcemap: true
  }
}
```

If you're using code transpiler plugins (such as Typescript), ensure to enable source-mapping there as well.

## Set up `@backtrace-labs/vite-plugin`

### Construct an upload URL

A specific URL is required to upload source maps. Follow [these instructions](https://docs.saucelabs.com/error-reporting/project-setup/submission-url/) to create an upload URL for the `sourcemap` endpoint with a `symbol-post` token.

### Install `@backtrace-labs/vite-plugin` as a developer dependency:

```bash
> npm install --save-dev @backtrace-labs/vite-plugin
```

### Add it to your `plugins` array in `vite.config.js`:

```js
import { BacktracePlugin } from '@backtrace-labs/vite-plugin';
// or
const { BacktracePlugin } = require('@backtrace-labs/vite-plugin');

module.exports = {
  // other configuration
  plugins: [new BacktracePlugin({
    // enable upload only on production builds
    uploadUrl: process.env.NODE_ENV === "production" ? "<your upload URL>" : undefined
  })]
}
```
npm package: @bacons/css-to-expo-linear-gradient
Description: Convert a CSS linear gradient function to expo-linear-gradient props
Author: Evan Bacon
Latest version: 1.3.0

# @bacons/css-to-expo-linear-gradient

> Demo: [snack](https://snack.expo.dev/@bacon/bacons-css-to-expo-linear-gradient)

Convert a CSS linear gradient function to `expo-linear-gradient` props.

## Add the package to your npm dependencies

```
yarn add @bacons/css-to-expo-linear-gradient
```

## Usage

```tsx
import { fromCSS } from "@bacons/css-to-expo-linear-gradient";
import { LinearGradient } from "expo-linear-gradient";

function App() {
  return (
    <LinearGradient
      {...fromCSS(
        `linear-gradient(0deg, #ff008450 0%, #fca40040 25%, #ffff0030 40%, #00ff8a20 60%, #00cfff40 75%, #cc4cfa50 100%);`
      )}
    />
  );
}
```

## Attribution

Most of the code is adapted from [this project](https://github.com/niklasvh/html2canvas/tree/eeda86bd5e81fb4e97675fe9bee3d4d15899997f) which converts CSS linear gradients to canvas gradients.
npm package: @badmachine/influxdb3-napi
Description: Influxdb3 client written in rust and built for nodejs with napi-rs
Latest version: 1.0.10

<p align="center">
  <img src="https://github.com/user-attachments/assets/8a984535-1704-44af-ba85-bd6859f99949" alt="influxdb3-napi Logo" width="300"/>
</p>

# influxdb3-napi

High-performance Node.js client for InfluxDB 3.0 with native Rust bindings, supporting both read and write operations.

## Installation

```bash
npm install @badmachine/influxdb3-napi
```

## Features

- **High Performance** - Native Rust bindings for optimal performance
- **SQL Queries** - Execute SQL queries with async iterator support
- **Line Protocol Writing** - Write data using InfluxDB line protocol
- **TypeScript Support** - Full TypeScript definitions included
- **Type Safe** - Built with type safety in mind

# Why?
- This library was initially inspired by the need to handle edge cases where other libraries fail to decode certain Arrow Flight data types (see [InfluxCommunity/influxdb3-js#590](https://github.com/InfluxCommunity/influxdb3-js/issues/590)). It correctly supports all data types returned by InfluxDB.
- **Unlike this library**, some requests to `https` hosts were failing with other JS libraries due to self-signed certificate check errors
-  ~~Blazingly™~~ Much  faster than other libraries when querying the data.
- Includes three different serializers for maximum flexibility:
  - **Default serializer** — conveniently converts time intervals.
  - **Serde-based serializer** — leverages `serde` for basic json serialization.
  - **Raw serializer** — returns the raw byte array buffer.

## Quick Start

```javascript
import { InfluxDbClient, Point } from '@badmachine/influxdb3-napi';

// Initialize client
const client = new InfluxDbClient(
  'http://your-influxdb-host:8086',
  'your-api-token'
);

// Write data using Point builder
const point = Point.fromMeasurement('temperature')
  .setTag('location', 'office')
  .setTag('sensor', 'temp01')
  .setBooleanField('active', true)
  .setFloatField('value', 23.5);

const lineProtocol = point.toLineProtocol('ns');
await client.write([lineProtocol], 'your-database');

// Query data with async iteration
const result = client.query({
  database: 'your-database',
  query: 'SELECT * FROM temperature WHERE time > now() - 1h',
  type: 'sql'
});

// Stream results efficiently
for await (const row of result) {
  console.log(row);
}
```

## TypeScript Support

Full TypeScript definitions are included:

## Contributing

Contributions are welcome! Please read our contributing guidelines and submit pull requests to our repository.

## License

MIT License - see LICENSE file for details.

## Support

- [Documentation](https://github.com/badmachine/influxdb3-napi)
- [Issue Tracker](https://github.com/badmachine/influxdb3-napi/issues)
- [Discussions](https://github.com/badmachine/influxdb3-napi/discussions)

## Changelog

See [CHANGELOG.md](CHANGELOG.md) for version history and changes.
npm package: @badmachine/influxdb3-napi-android-arm-eabi
Description: Influxdb3 client written in rust and built for nodejs with napi-rs
Latest version: 1.0.10

# `@badmachine/influxdb3-napi-android-arm-eabi`

This is the **armv7-linux-androideabi** binary for `@badmachine/influxdb3-napi`