open-index/open-npm huggingface dataset:
npm package: @spectrum/ra-language-korean
Description: Korean Messages for React-Admin
Author: spectrum
Latest version: 0.0.8

# Korean Messages for React-Admin
Korean Messages for React-Admin, the frontend framework for building admin applications on top of REST/GraphQL services.

# Installation
```
npm install --save @spectrum/ra-language-korean
```

# Usage
```
import koreanMessages from '@spectrum/ra-language-korean';
import polyglotI18nProvider from 'ra-i18n-polyglot';

const messages = {
    'ko': koreanMessages,
};
const i18nProvider = polyglotI18nProvider(locale => messages[locale]);

<Admin locale="ko" i18nProvider={i18nProvider}>
  ...
</Admin>
```

# License
This translation is licensed under the MIT License.
npm package: @spectrum/ra-language-spanish
Description: Spanish Messages for React-Admin
Author: spectrum
Latest version: 0.0.1

# Spanish Messages for React-Admin

Spanish Messages for React-Admin, the frontend framework for building admin applications on top of REST/GraphQL services.

# Installation

```
npm install --save @spectrum/ra-language-spanish
```

# Usage

```
import spanishMessages from '@spectrum/ra-language-spanish';
import polyglotI18nProvider from 'ra-i18n-polyglot';

const messages = {
    'es': spanishMessages,
};
const i18nProvider = polyglotI18nProvider(locale => messages[locale]);

<Admin locale="es" i18nProvider={i18nProvider}>
  ...
</Admin>
```

# License

This translation is licensed under the MIT License.
npm package: @spectrumlabs/analytics
Description: Amplitude analytics lib for Spectrum Finance dApps.
Latest version: 1.1.9

# @spectrumlabs/analytics

[![npm version](https://badge.fury.io/js/@spectrumlabs%2Fanalytics.svg)](https://badge.fury.io/js/@spectrumlabs%2Fanalytics)

The `@spectrumlabs/analytics` package is used across Spectrum Finance applications to gather non-identified user data and improve those products using this data.

The package uses `@amplitude/analytics-browser` (Amplitude SDK) under the hood.

## Legal notice

Spectrum Labs encourages integrators to evaluate their own regulatory obligations when integrating this package into their products, including, but not limited to, those related to economic or trade sanctions compliance.
npm package: @specui/cli
Description: Build UIs with Specs
Author: Chris Tate
Latest version: 0.2.5

# @spec-ui/cli

> the CLI of SpecUI

## Quickstart

### Use `npx`

```
npx @specui/cli [command]
```

### Install Globally

First install:

```
npm i -g specui
```

Then run:

```
specui [command]
```

## Commands

### `generate`

Generates UI from spec

### `new`

Creates a new SpecUI project
npm package: @specup/editor
Description: Xen prosemirror editor
Latest version: 2.1.0

# XEN Editor

Xen prosemirror editor

## Installation

### Peer Dependencies

```bash
yarn add react styled-components bulma
```

## Usage

```jsx
import 'bulma/css/bulma.css'
import '@specup/editor/dist/style.css'
import { Editor } from '@specup/editor'

const EditorContainer = () => {
  const ref = useRef(null)
  const [html, setHTML] = useState(null)

  function handlePrintClick() {
    if (ref.current) {
      setHTML(ref.current.html())
    }
  }

  return (
    <>
      <StyledEditor
        initialValue={`
          <p style="text-align: center">Buddy</p>
          <p>Hello</p>
          <p><span style="color: red;">World</span></p>
          <p style="margin-left: 40px">Indented</p>
        `}
        apiBaseURL="https://graphql.linkareer.com/graphql"
        ref={ref}
      />
      <button onClick={handlePrintClick}>Print</button>
      {html && <div dangerouslySetInnerHTML={{ __html: html }} />}
    </>
  )
}
```

## Deploy

```sh
npm login
npm version <patch | major | minor...> && npm publish
```

## Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

## License

[MIT](https://choosealicense.com/licenses/mit/)
npm package: @specverse/engine-registry
Description: SpecVerse registry client — cache, validation, offline support for the community library platform
Latest version: 4.0.4

# @specverse/engine-registry

Registry client for the SpecVerse community library platform.

## Features

- **Registry client** — search, fetch, and resolve specs from the community registry
- **Cache manager** — local caching with TTL for registry responses
- **Offline handler** — graceful fallback when registry is unreachable
- **Manifest validator** — validate implementation manifests against registry
- **Installation validator** — verify installed packages match manifest
- **Error formatter** — structured error reporting for validation results

## Usage

```typescript
import { Validator, ErrorFormatter, RegistryClient } from '@specverse/engine-registry';

// Validate a manifest
const validator = new Validator();
const result = await validator.validate({
  manifest: { filePath: 'manifests/implementation.yaml' },
  installation: { projectRoot: process.cwd() }
});

// Format results
const formatter = new ErrorFormatter();
formatter.format(result);
```

## API

| Export | Purpose |
|--------|---------|
| `RegistryClient` | HTTP client for the registry API |
| `CacheManager` | Local cache with TTL management |
| `OfflineHandler` | Fallback when registry unavailable |
| `Validator` | Orchestrates manifest + installation validation |
| `ManifestValidator` | Validates manifest structure and factory references |
| `InstallationValidator` | Checks installed packages against manifest |
| `ErrorFormatter` | Formats validation results for CLI output |
| `manifestConfigToSpecVerseManifest` | Converts manifest config to validation format |
| `validateFactoryReferences` | Checks factory references in capability mappings |
npm package: @specverse/types
Description: Shared type definitions for SpecVerse engines — AST, specs, engine interfaces
Latest version: 4.1.4

# @specverse/types

Shared type definitions for all SpecVerse engine packages — AST types, engine interfaces, entity module types, and processor abstractions.

## Purpose

This is the foundation package of the SpecVerse engine ecosystem. It defines the TypeScript types and interfaces that all other engine packages depend on, ensuring a consistent type contract across the parser, inference, realize, and entity systems. It also breaks the circular dependency between parser and entities by housing processor abstractions here.

## Installation

```bash
npm install @specverse/types
```

## Dependencies

None. This package has zero runtime dependencies — it exports only type definitions and a small utilities module.

## Key Exports

| Export | Type | Description |
|--------|------|-------------|
| `SpecVerseAST` | type | Root AST node produced by the parser |
| `ComponentSpec`, `ModelSpec` | type | Individual component specifications within the AST |
| `SpecVerseEngine`, `ParserEngine`, `InferenceEngine`, `RealizeEngine` | interface | Engine contracts for the registry discovery system |
| `EngineInfo` | type | Metadata returned by `engine.getInfo()` |
| `ParseResult`, `ParseOptions` | type | Parser input/output types |
| `ProcessorContext`, `AbstractProcessor` | type/class | Processor abstractions shared between parser and entities |
| `EntityModule`, `EntityRegistryInterface` | type | Entity module system contracts |
| `EntityConventionProcessor`, `EntityInferenceRule`, `EntityGenerator` | type | Facet interfaces for entity modules |
| `pluralize` | function | Naive English pluralizer used across engine packages |

## Usage

```typescript
import type { SpecVerseAST, ModelSpec, ParserEngine } from '@specverse/types';

function inspectModels(ast: SpecVerseAST): void {
  for (const [name, model] of Object.entries(ast.models ?? {})) {
    console.log(`Model: ${name}, fields: ${Object.keys(model.attributes ?? {}).length}`);
  }
}
```

## Architecture

```
src/
├── ast.ts             # AST node types (SpecVerseAST, ModelSpec, ComponentSpec, etc.)
├── engine.ts          # Engine interfaces (ParserEngine, InferenceEngine, RealizeEngine)
├── processor.ts       # ProcessorContext and AbstractProcessor (breaks parser ↔ entities cycle)
├── entity-module.ts   # Entity module system types (EntityModule, facet interfaces)
├── utils.ts           # Small shared utilities (pluralize)
└── index.ts           # Barrel re-export
```

## See Also

- [@specverse/engine-entities](../entities/) — Entity module system that implements the types defined here
- [@specverse/engine-parser](../parser/) — Parser engine that produces `SpecVerseAST`
npm package: @specweave/mcp-client
Description: SpecWeave MCP client for Claude Code and other MCP-compatible tools (stdio transport)
Author: SpecWeave
Latest version: 1.0.0

# @specweave/mcp-client

SpecWeave MCP client for Claude Code and other MCP-compatible tools.

## Installation

```bash
npm install -g @specweave/mcp-client
```

Or use with `npx` (no installation required):

```bash
npx -y @specweave/mcp-client
```

## Usage

### Get Your Access Token

1. Log in to SpecWeave
2. Navigate to your account settings
3. Create a new MCP access token
4. Select your application and required scopes
5. Copy the generated token

### Configure Claude Code

Add to your `.mcp.json`:

```json
{
  "mcpServers": {
    "specweave": {
      "command": "npx",
      "args": ["-y", "@specweave/mcp-client"],
      "env": {
        "SPECWEAVE_TOKEN": "your_token_here"
      }
    }
  }
}
```

## License

MIT
npm package: @specwise/runner
Description: Local test runner for Specwise — executes test cases on your machine with Playwright
Latest version: 0.2.3

# @specwise/runner

Local test runner for [Specwise](https://specwise.wearesnx.studio) - executes test cases on your machine using Playwright.

## Usage

Generate a token from your Specwise dashboard (Test Runs > Run Locally), then:

```bash
npx @specwise/runner --token=<token> --api=<api-url>
```

### Options

| Flag | Description |
|------|-------------|
| `--token` | Execution token from Specwise (required) |
| `--api` | Specwise API base URL (required) |
| `--headed` | Show browser window (default: headless) |
| `--help` | Show help |

### Example

```bash
npx @specwise/runner \
  --token=eyJhbGciOiJIUzI1NiJ9... \
  --api=https://api.specwise.wearesnx.studio
```

## How it works

1. Pulls test cases and pipelines from the Specwise API
2. Records pipelines for test cases that don't have one yet
3. Executes each test case in a Chromium browser via Playwright
4. Captures screenshots at each step
5. Reports results back to the Specwise dashboard

## Requirements

- Node.js 18+
- Chromium is installed automatically via Playwright on first run

## Exit codes

- `0` - All tests passed
- `1` - One or more tests failed
npm package: @specwright/mcp-server
Description: MCP server for E2E test automation — configure, explore, plan, and check pipeline status
Latest version: 0.1.0

# @specwright/mcp-server

MCP server for E2E test automation. Provides 5 tools for configuring, exploring, planning, and automating Playwright BDD test generation.

## Tools

| Tool | Description |
|------|-------------|
| `e2e_configure` | Init setup, read/list/add entries in `instructions.js` |
| `e2e_explore` | Get exploration plan with auth status, known selectors, step-by-step instructions |
| `e2e_plan` | Generate `seed.spec.js` + test plan markdown from discovered selectors |
| `e2e_status` | Check pipeline state — config, seed file, plans, test results |
| `e2e_automate` | Read `instructions.js` and return full pipeline execution plan |

## Usage with Claude Code

Add to your project's `.mcp.json`:

```json
{
  "mcpServers": {
    "e2e-automation": {
      "command": "npx",
      "args": ["@specwright/mcp-server"]
    }
  }
}
```

Then use the `/e2e-desktop-automate` skill (from `@specwright/plugin`) or call tools directly.

## Usage with Claude Desktop

Add to `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "e2e-automation": {
      "command": "npx",
      "args": ["@specwright/mcp-server"],
      "env": {
        "PROJECT_ROOT": "/path/to/your/project"
      }
    },
    "microsoft-playwright": {
      "command": "npx",
      "args": ["@playwright/mcp@latest"]
    }
  }
}
```

## Environment Variables

| Variable | Default | Description |
|----------|---------|-------------|
| `PROJECT_ROOT` | `process.cwd()` | Project root directory |
| `BASE_URL` | `http://localhost:5173` | Application URL for exploration |
| `AUTH_REQUIRED` | `true` | Whether authentication is needed |
| `AUTH_DATA` | — | JSON object with auth credentials |

## Part of Specwright

This MCP server is part of the [Specwright](https://github.com/SanthoshDhandapani/specwright) E2E test automation platform. Install the full framework with:

```bash
npx @specwright/plugin init
```
npm package: @specy/stack-context
Description: A library to store data anywhere in a call stack, only in sync code
Author: Specy
Latest version: 0.0.2

# Stack context
A library to store data inside of the stack, so you can retrieve it anywhere in the call stack, only in sync code.

It was an experiment to replicate `AsyncLocalStorage`, which works, but only for sync code (could be made much simpler, just wanted to experiment with storing things in the stack)

```ts
import { StackContext } from "@specy/stack-context";

type MyState = {
  a: number;
  b: number;
};

function sum() {
  const state = StackContext.state<MyState>();
  const sum = state.a + state.b;
  console.log(`The sum is: `, sum);
}

StackContext.root(
  () => {
    sum();
  },
  { a: 10, b: 20 },
);
```
npm package: @spedn/cli
Description: Spedn compiler CLI
Author: {o} Software
Latest version: 5.0.0

Spedn
=================================

![logo](https://bytebucket.org/o-studio/spedn/raw/6c4c092ed4615a51b5e8a37cd68b2175e0ed826d/images/spedn-logo-cashwave-144.png "Spedn")

Spedn is a high level smart contracts programming language for electronic cash.
It compiles to Script dialects in eCash, Bitcoin Cash, Lotus and Bitcoin.
It is designed for explicitness and safety.

* It is statically typed - detects many errors at compile time
* It is explicitly typed - no guessing what the expression is supposed to return
* It is purely-functional - free of side effects, the common source of bugs
* It has a familiar C-like syntax

This package contains a command-line tool for compiling contracts. For usage instructions, type:

`spedn --help`

If you want to use Spedn compiler as a NodeJS library, use [@spedn/sdk](https://www.npmjs.com/package/@spedn/sdk).

If you want to run contracts created with Spedn in your blockchain app, use [@spedn/rts-bchjs](https://npmjs.com/packages/@spedn/bchjs-rts).

[Spedn Home Page](https://spedn.pl)

[Full Docs](http://spedn.rtfd.io)

Donations: 🎺 Pein#7306 || ecash:qp8x5wakcts248drk5apn4k09a53qclcevjayr77xh || bitcoincash:qrc2jhalczuka8q3dvk0g8mnkqx79wxp9gvvqvg7qt
[![Sponsors](https://rcimg.net/images/sponsors/svg/pein.svg)](https://read.cash/become-a-sponsor/pein)
npm package: @spedn/rts
Description: Runtime System for Spedn contracts.
Author: {o} Software
Latest version: 5.0.0

Spedn Runtime
=================================

![logo](https://bytebucket.org/o-studio/spedn/raw/6c4c092ed4615a51b5e8a37cd68b2175e0ed826d/images/spedn-logo-cashwave-144.png "Spedn")

Spedn is a high level smart contracts programming language for electronic cash.
It compiles to Script dialects in eCash, Bitcoin Cash, Lotus and Bitcoin.
It is designed for explicitness and safety.

* It is statically typed - detects many errors at compile time
* It is explicitly typed - no guessing what the expression is supposed to return
* It is purely-functional - free of side effects, the common source of bugs
* It has a familiar C-like syntax

This package contains a lightweight, SDK-agnostic runtime for blockchain applications using compiled Spedn contracts.
To integrate your contract into an app built on top of one of the SDKs, use the apropriate adapter:

* [@spedn/rts-bchjs](https://npmjs.com/packages/@spedn/bchjs-rts) - for apps on top of [BCH-JS](https://www.npmjs.com/package/@psf/bch-js)

Install this package directly only if you want to develop your own adapter.

If you want to dynamically compile Spedn contracts in your app, also install [@spedn/sdk](https://www.npmjs.com/package/@spedn/sdk).

If you want to use Spedn compiler as a command-line tool, install [@spedn/cli](https://www.npmjs.com/package/@spedn/cli).

[Spedn Home Page ](https://spedn.pl)

[Full Docs](http://spedn.rtfd.io)

Donations: 🎺 Pein#7306 || ecash:qp8x5wakcts248drk5apn4k09a53qclcevjayr77xh || bitcoincash:qrc2jhalczuka8q3dvk0g8mnkqx79wxp9gvvqvg7qt
[![Sponsors](https://rcimg.net/images/sponsors/svg/pein.svg)](https://read.cash/become-a-sponsor/pein)
npm package: @spedn/rts-bchjs
Description: Runtime System for Spedn Contracts with BCH-JS adapter
Author: {o} Software
Latest version: 5.0.0

Spedn Runtime for BCH-JS
=================================

![logo](https://bytebucket.org/o-studio/spedn/raw/6c4c092ed4615a51b5e8a37cd68b2175e0ed826d/images/spedn-logo-cashwave-144.png "Spedn")

Spedn is a high level smart contracts programming language for electronic cash.
It compiles to Script dialects in eCash, Bitcoin Cash, Lotus and Bitcoin.
It is designed for explicitness and safety.

* It is statically typed - detects many errors at compile time
* It is explicitly typed - no guessing what the expression is supposed to return
* It is purely-functional - free of side effects, the common source of bugs
* It has a familiar C-like syntax

This package contains a [BCH-JS](https://www.npmjs.com/package/@psf/bch-js) runtime for Bitcoin Cash applications using compiled Spedn contracts.

If you want to dynamically compile Spedn contracts in your app, also install [@spedn/sdk](https://www.npmjs.com/package/@spedn/sdk).

If you want to use Spedn compiler as a command-line tool, install [@spedn/cli](https://www.npmjs.com/package/@spedn/cli).

[Spedn Home Page ](https://spedn.pl)

[Full Docs](http://spedn.rtfd.io)

Donations: 🎺 Pein#7306 || ecash:qp8x5wakcts248drk5apn4k09a53qclcevjayr77xh || bitcoincash:qrc2jhalczuka8q3dvk0g8mnkqx79wxp9gvvqvg7qt
[![Sponsors](https://rcimg.net/images/sponsors/svg/pein.svg)](https://read.cash/become-a-sponsor/pein)
npm package: @spedn/rts-bitbox
Description: Runtime System for Spedn Contracts with BITBOX adapter
Author: {o} Software
Latest version: 3.1.1
Deprecated: This package is still maintained but BITBOX-SDK is not. We recommend migrating to BCH-JS which has a very similar API.

Spedn Runtime for BCH-JS
=================================

![logo](https://bytebucket.org/o-studio/spedn/raw/6c4c092ed4615a51b5e8a37cd68b2175e0ed826d/images/spedn-logo-cashwave-144.png "Spedn")

Spedn is a high level smart contracts language for Bitcoin Cash.
It is designed for explicitess and safety:

* It is statically typed - detects many errors at compile time
* It is explicitly typed - no guessing what the expression is supposed to return
* It is purely-functional - free of side effects, the common source of bugs
* It has a familiar C-like syntax

This package contains a [BCH-JS](https://www.npmjs.com/package/@psf/bch-js) runtime for Bitcoin Cash applications using compiled Spedn contracts.

If you want to dynamically compile Spedn contracts in your app, also install [@spedn/sdk](https://www.npmjs.com/package/@spedn/sdk).

If you want to use Spedn compiler as a command-line tool, install [@spedn/cli](https://www.npmjs.com/package/@spedn/cli).

[Spedn Home Page ](https://spedn.pl)

[Full Docs](http://spedn.rtfd.io)

Donations: 🎺 Pein#7306 || bitcoincash:qrc2jhalczuka8q3dvk0g8mnkqx79wxp9gvvqvg7qt
[![Sponsors](https://rcimg.net/images/sponsors/svg/pein.svg)](https://read.cash/become-a-sponsor/pein)
npm package: @spedn/sdk
Description: Spedn compiler SDK
Author: {o} Software
Latest version: 5.0.0

Spedn
=================================

![logo](https://bytebucket.org/o-studio/spedn/raw/6c4c092ed4615a51b5e8a37cd68b2175e0ed826d/images/spedn-logo-cashwave-144.png "Spedn")

Spedn is a high level smart contracts programming language for electronic cash.
It compiles to Script dialects in eCash, Bitcoin Cash, Lotus and Bitcoin.
It is designed for explicitness and safety.

* It is statically typed - detects many errors at compile time
* It is explicitly typed - no guessing what the expression is supposed to return
* It is purely-functional - free of side effects, the common source of bugs
* It has a familiar C-like syntax

This package contains an SDK for compiling Spedn contract in NodeJS apps.

If you want to use Spedn as a command-line tool, use [@spedn/cli](https://www.npmjs.com/package/spedn-cli).

If you want to run a compiled contract:

* install [@spedn/rts-bchjs](https://npmjs.com/packages/@spedn/rts-bchjs) - a runtime using [BCH-JS](https://www.npmjs.com/package/@psf/bch-js)
* develop your own runtime by implementing interfaces defined in [@spedn/rts](https://npmjs.com/packages/@spedn/rts)

[Spedn Home Page](https://spedn.pl)

[Full Docs](http://spedn.rtfd.io)

Donations: 🎺 Pein#7306 || ecash:qp8x5wakcts248drk5apn4k09a53qclcevjayr77xh || bitcoincash:qrc2jhalczuka8q3dvk0g8mnkqx79wxp9gvvqvg7qt
[![Sponsors](https://rcimg.net/images/sponsors/svg/pein.svg)](https://read.cash/become-a-sponsor/pein)