open-index/open-npm huggingface dataset:
npm package: @pluxbox/integration-toolbox
Description: Package for jwt authentication for integration in the Pluxbox Platform.
Latest version: 0.0.1

# Pluxbox Integrations Toolbox

## Validate Platform Jwt Token

Validates [JWT](https://jwt.io) tokens from the platform. They payload will return in a structure defined link
this [json schema](./jwt-payload.schema.json). The token will also include the authentication information.

This payload is validated using the `EdDSA` algorithm. In the platform a public and private key pair are generated. The
public key is visible in the integration crud. This key can be used to
validate the received token in the request. Tokens will always be sent in the Authorization header. See example request
bellow:

```http request
POST https://example.com/graphql
Content-Type: application/json
Authorization: JWT jwt_token_from_the_platform_that_needs_to_be_validated

{"query":"{ __typename }"}
```
npm package: @pluxel/core
Description: Demo example that imports a local package
Latest version: 0.2.10

# CHANGE

- 0.2.0
我们意识到 @Optional 的多余，因为你总是要导入一个包才能声明可选依赖，而可选依赖的意义就是包可能不存在，这是x相悖的。
现在的设计思路是，轻量的可选逻辑通过 afterCommit hook 完成更改，而重量级的可选请独立成一个插件，插件本身具有可选性，
极大提高了内部状态的清晰度，以便架构能更好的开发。
npm package: @pluxel/market
Description: Developer toolkit for the Pluxel marketplace ecosystem. The package bundles two things:
Latest version: 0.1.0

# @pluxel/market

Developer toolkit for the Pluxel marketplace ecosystem. The package bundles two things:

1. **GitHub Actions** under `actions/` for publishing plugins and validating manifests.
2. **Hono RPC helpers** under `src/` so dashboards or CLIs can talk to the worker with end-to-end typing.

## RPC client

```ts
import { createMarketRpcClient } from "@pluxel/market";

const client = createMarketRpcClient({
  baseUrl: "https://worker.example.com",
  headers: async () => ({
    Authorization: `Bearer ${await getToken()}`,
  }),
});

// Health check
await client.health();

// Get the latest snapshot (flat package list + tags)
const snapshot = await client.snapshots.current();

// Get summary statistics (version, counts)
const stats = await client.snapshots.stats();

// Publish a package
await client.webhook.submit(
  { packageName: "pluxel-plugin-example", version: "1.0.0" },
  githubOidcToken
);
```

`createMarketRpcClient` accepts either a base URL string (legacy signature) or a full options object with:

- `headers` / `init` / `fetch` hooks for SSR, custom auth, or alternative runtimes
- `routes` overrides when the worker is reverse-proxied
- `.request(path, init)` escape hatch for custom endpoints

`renderSnapshotDashboard` still mounts the full React dashboard, but it now accepts a `snapshotSource` option so you can hydrate from any loader (REST, GraphQL, gRPC) without pulling in the RPC client. Pass `client` **or** `snapshotSource`, plus the existing knobs:

- `appearance` (`"light"`/`"dark"`)
- cached embeds via `initialSnapshot` + `hydrateOnInit={false}`
- `resolveMetadata` + `tagDictionary` for repo URLs, tag IDs, highlights, version history, etc.
- `enableInstallQueue` + `onInstallSubmit` to surface batch install
- `namePrefixesToTrim` (e.g. `["pluxel-plugin-"]`) to hide redundant prefixes

Both the component and the renderer share the same props (`DashboardOptions` / `SnapshotDashboardProps`), so they can be reused in your own React tree without touching the DOM helper.

## Building

```
bun run --filter @pluxel/market build
```