open-index/open-npm huggingface dataset:
npm package: @harmonyos-dev/highlightjs-arks
Description: ArkTS highlight.js extension
Author: h@phodal.com
Latest version: 0.0.4
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# Highlight.js ArkTS support

# Deprecated in favor of [highlightjs-arkts](https://www.npmjs.com/package/@harmonyos-dev/highlightjs-arkts)

The Highlight.js plugin for HarmonyOS's ArkTS

Online Demo: https://harmonyos-dev.github.io/aigc-harmonyos-sample/

## Static website or simple usage

```html
<script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release/build/highlight.min.js"></script>
<script
  type="text/javascript"
  src="https://cdn.jsdelivr.net/npm/@harmonyos-dev/highlightjs-arks@0.0.2/src/languages/arkts.js"></script>
```

## With Node

```javascript
var hljs = require('highlightjs');
var hljsArkts = require('@harmonyos-dev/highlightjs-arks');

hljs.registerLanguage('arkts', hljsArkts);
hljs.highlightAll();
```

## TODOs:

- [x] publish to npm
- [x] rebuild project
- [ ] ...


## License

Highlight.js is released under the BSD 3-Clause License. See LICENSE file for details. Highlightjs-arkts is released 
under the MIT License. See LICENSE file for details.
npm package: @harmonyos-dev/highlightjs-arkts
Description: ArkTS highlight.js extension
Author: h@phodal.com
Latest version: 0.0.5

# Highlight.js ArkTS support

The Highlight.js plugin for HarmonyOS's ArkTS

Online Demo: https://harmonyos-dev.github.io/aigc-harmonyos-sample/

## Static website or simple usage

```html
<script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release/build/highlight.min.js"></script>
<script
  type="text/javascript"
  src="https://cdn.jsdelivr.net/npm/@harmonyos-dev/highlightjs-arks@0.0.2/src/languages/arkts.js"></script>
```

## With Node

```javascript
var hljs = require('highlightjs');
var hljsArkts = require('@harmonyos-dev/highlightjs-arks');

hljs.registerLanguage('arkts', hljsArkts);
hljs.highlightAll();
```

## TODOs:

- [x] publish to npm
- [x] rebuild project
- [ ] ...


## License

Highlight.js is released under the BSD 3-Clause License. See LICENSE file for details. Highlightjs-arkts is released 
under the MIT License. See LICENSE file for details.
npm package: @harneon-ai/githeat
Description: MCP Server for Git heatmap analysis - provides AI Agents with Git commit activity and contributor pattern insights
Author: harneon-ai
Latest version: 0.1.1

# @harneon-ai/githeat

一个 MCP (Model Context Protocol) Server，为 AI 助手提供 Git 提交热力图分析能力。

## 功能概览

- 收集 Git 仓库提交数据
- 生成仓库级统计信息（每日活动、贡献者摘要、文件类型分布）
- 分析特定作者的提交模式和活跃度
- 查询特定作者的所有提交记录

## 快速开始

### 1. 使用 npx（推荐）

```bash
npx @harneon-ai/githeat
```

### 2. 全局安装

```bash
npm install -g @harneon-ai/githeat
harneon-githeat
```

### 3. 在 Claude Code 中使用

```bash
claude mcp add harneon-githeat -- harneon-githeat
```

### 4. 在 Claude Desktop 中使用

编辑 Claude Desktop 配置文件（`claude_desktop_config.json`）：

```json
{
  "mcpServers": {
    "harneon-githeat": {
      "command": "harneon-githeat"
    }
  }
}
```

## MCP 工具说明

### 1. collect-commits

收集 Git 仓库的提交数据。

**参数：**
- `repo` (必需): 仓库路径（本地）或 URL（远程）
- `branch` (可选): 要分析的分支，默认为当前分支
- `allBranches` (可选): 是否分析所有分支，默认为 false
- `maxCount` (可选): 最大提交数量，默认为 10000

**返回：**
- `sessionId`: 会话 ID，用于后续分析工具
- `commitsFilePath`: 提交数据 JSON 文件路径
- `totalCommits`: 总提交数

### 2. repo-stats

生成仓库级统计信息。

**参数：**
- `sessionId` (必需): 来自 collect-commits 的会话 ID

**返回：**
- `statsFilePath`: 统计数据 JSON 文件路径，包含每日活动、作者摘要、文件类型分布

### 3. author-stats

分析特定作者的提交统计。

**参数：**
- `sessionId` (必需): 来自 collect-commits 的会话 ID
- `author` (必需): 作者名称（不区分大小写）

**返回：**
- `statsFilePath`: 作者统计数据 JSON 文件路径

### 4. query-by-author

查询特定作者的所有提交。

**参数：**
- `sessionId` (必需): 来自 collect-commits 的会话 ID
- `author` (必需): 作者名称（不区分大小写）

**返回：**
- `queryFilePath`: 查询结果 JSON 文件路径，包含按日期排序的提交列表
- `totalCommits`: 该作者的提交总数

## 开发

### 安装依赖

```bash
npm install
```

### 构建

```bash
npm run build
```

### 测试

```bash
npm test
```

### 开发模式

```bash
npm run dev
```

## 技术栈

- Node.js >= 18.0.0
- TypeScript
- MCP SDK
- Zod

## 许可证

MIT
npm package: @harness-engineering/cli
Description: CLI for Harness Engineering toolkit
Latest version: 1.24.0

# @harness-engineering/cli

CLI for Harness Engineering toolkit.

## Installation

```bash
npm install -g @harness-engineering/cli
```

## Commands

### `harness init`

Initialize a new harness-engineering project.

```bash
harness init
harness init --name my-project
```

### `harness validate`

Run all validation checks.

```bash
harness validate
harness validate --json
harness validate --verbose
```

### `harness check-deps`

Validate dependency layers and detect circular dependencies.

```bash
harness check-deps
```

### `harness check-docs`

Check documentation coverage.

```bash
harness check-docs
harness check-docs --min-coverage 90
```

### `harness cleanup`

Detect entropy issues.

```bash
harness cleanup
harness cleanup --type drift
harness cleanup --type dead-code
```

### `harness fix-drift`

Auto-fix entropy issues.

```bash
harness fix-drift           # Dry run
harness fix-drift --no-dry-run  # Apply fixes
```

### `harness add`

Add components to the project.

```bash
harness add layer services
harness add module user
harness add doc architecture
```

### `harness agent`

Agent orchestration commands.

```bash
harness agent run review
harness agent review
```

## Global Options

- `--config <path>` - Path to config file
- `--json` - Output as JSON
- `--verbose` - Verbose output
- `--quiet` - Minimal output

## Configuration

Create `harness.config.json` in your project root:

```json
{
  "version": 1,
  "name": "my-project",
  "layers": [
    { "name": "types", "pattern": "src/types/**", "allowedDependencies": [] },
    { "name": "domain", "pattern": "src/domain/**", "allowedDependencies": ["types"] }
  ],
  "agentsMapPath": "./AGENTS.md",
  "docsDir": "./docs"
}
```

## Exit Codes

- `0` - Success
- `1` - Validation failed
- `2` - Error
npm package: @harness-engineering/linter-gen
Description: Generate ESLint rules from YAML configuration
Latest version: 0.1.6

# @harness-engineering/linter-gen

Generate ESLint rules from YAML configuration using extensible Handlebars templates.

## Installation

```bash
pnpm add @harness-engineering/linter-gen
```

## Usage

### Configuration

Create `harness-linter.yml`:

```yaml
version: 1
output: ./generated/eslint-rules

rules:
  - name: no-ui-in-services
    type: import-restriction
    severity: error
    config:
      source: 'src/services/**'
      forbiddenImports:
        - 'react'
        - 'src/ui/**'
      message: 'Service layer cannot import UI code'
```

### CLI

```bash
# Generate rules
harness linter generate

# Generate with options
harness linter generate --config ./custom-config.yml --output ./rules --clean

# Validate config only
harness linter validate
```

### Programmatic API

```typescript
import { generate, validate } from '@harness-engineering/linter-gen';

// Generate rules
const result = await generate({
  configPath: './harness-linter.yml',
  outputDir: './generated',
  clean: true,
});

if (result.success) {
  console.log(`Generated ${result.rulesGenerated.length} rules`);
}

// Validate config
const validation = await validate({ configPath: './harness-linter.yml' });
```

## Built-in Templates

### import-restriction

Block imports matching patterns in files matching a source pattern.

```yaml
- name: no-react-in-services
  type: import-restriction
  config:
    source: 'src/services/**'
    forbiddenImports:
      - 'react'
      - 'react-dom'
    message: 'Service files cannot import React'
```

### boundary-validation

Ensure files export Zod schemas for validation.

```yaml
- name: api-must-validate
  type: boundary-validation
  config:
    pattern: 'src/api/**/*.ts'
    requireZodSchema: true
    message: 'API endpoints must use Zod validation'
```

### dependency-graph

Detect circular import dependencies.

```yaml
- name: no-cycles
  type: dependency-graph
  config:
    entryPoints:
      - 'src/index.ts'
    exclude:
      - '**/*.test.ts'
    maxDepth: 20
```

## Custom Templates

### Convention-based

Place templates in `templates/` directory relative to config:

```
project/
├── harness-linter.yml
└── templates/
    └── my-custom-type.ts.hbs
```

### Explicit paths

Specify template paths in config:

```yaml
templates:
  my-custom-type: ./custom-templates/my-rule.ts.hbs
```

### Template Context

Templates receive:

```typescript
{
  name: 'rule-name',           // kebab-case
  nameCamel: 'ruleName',       // camelCase
  namePascal: 'RuleName',      // PascalCase
  severity: 'error',           // error | warn | off
  config: { ... },             // Template-specific config
  meta: {
    generatedAt: '2026-03-13T...',
    generatorVersion: '0.1.0',
    configPath: '/path/to/config.yml',
  }
}
```

### Handlebars Helpers

- `{{json value}}` - JSON.stringify
- `{{jsonPretty value}}` - JSON.stringify with formatting
- `{{camelCase "kebab-name"}}` - Convert to camelCase
- `{{pascalCase "kebab-name"}}` - Convert to PascalCase

## License

MIT
npm package: @harness-engineering/types
Description: TypeScript types and interfaces for Harness Engineering
Latest version: 0.9.1

# @harness-engineering/types

Shared TypeScript types for harness-engineering packages.

## Installation

```bash
npm install @harness-engineering/types
# or
pnpm add @harness-engineering/types
```

## Usage

```typescript
import { Result, Ok, Err, isOk, isErr } from '@harness-engineering/types';

// Create successful result
const success: Result<number, never> = Ok(42);

// Create error result
const failure: Result<never, string> = Err('Something went wrong');

// Type-safe error handling
function divide(a: number, b: number): Result<number, string> {
  if (b === 0) {
    return Err('Division by zero');
  }
  return Ok(a / b);
}

const result = divide(10, 2);
if (isOk(result)) {
  console.log(result.value); // 5
} else {
  console.error(result.error);
}
```

## API

### `Result<T, E>`

Type-safe error handling used across all harness-engineering APIs.

```typescript
type Result<T, E = Error> = { ok: true; value: T } | { ok: false; error: E };
```

### `Ok<T>(value: T)`

Creates a successful Result.

### `Err<E>(error: E)`

Creates a failed Result.

### `isOk<T, E>(result: Result<T, E>)`

Type guard to check if Result is Ok.

### `isErr<T, E>(result: Result<T, E>)`

Type guard to check if Result is Err.

### `UsageRecord`

Extended token usage entry for cost tracking. Composes `TokenUsage` with session metadata, cache token counts, model identifier, and cost in integer microdollars.

```typescript
import type { UsageRecord } from '@harness-engineering/types';
```

### `ModelPricing`

Per-model pricing rates in USD per 1 million tokens. Includes input, output, and optional cache read/write rates.

```typescript
import type { ModelPricing } from '@harness-engineering/types';
```

### `DailyUsage` / `SessionUsage`

Aggregated usage views for daily trends and per-session breakdowns. Used by `harness usage` CLI commands.

## License

MIT
npm package: @harness-kit/cli
Description: CLI tool that scaffolds AI agent harness environments for projects
Latest version: 0.1.1

# @harness-kit/cli

CLI tool that scaffolds AI agent harness environments for projects.

## Install

```bash
npm install -g @harness-kit/cli
# or use directly
npx @harness-kit/cli init
```

## Usage

```bash
harness-kit init                    # interactive wizard — detects existing config
harness-kit add typescript          # add a preset bundle
harness-kit add rules/python        # add a single artifact
harness-kit list                    # browse all available modules
harness-kit list --tag testing      # filter by tag
harness-kit info tdd-workflow       # detail + preview
harness-kit status                  # view installed harness state
```

## License

MIT
npm package: @harness-kit/core
Description: Shared constants and types for harness-kit
Latest version: 0.1.1

# @harness-kit/core

Shared constants and types for the harness-kit ecosystem.

This is an internal package used by `@harness-kit/cli`. You generally don't need to install it directly.

## Install

```bash
npm install @harness-kit/core
```

## License

MIT
npm package: @harness-ui/icons
Description: SVG-based React icon components
Author: Subigya Lamichhane
Latest version: 0.0.2

# SVG Icon Component Library for React

This is a starter project for an SVG-based icon component library for React, built using [SVGR](https://react-svgr.com/) and [Rollup](https://rollupjs.org/).

## Overview

Generate ready-made React components from `.svg` files using `@svgr/cli` and bundle them into a library using `rollup`. No need to write any React code yourself!

Watch the tutorial video [here](https://youtu.be/v0ZLEy1SE-A)!

## Plugins

The following plugins are utilized in this project:

**Rollup:**
- [@rollup/plugin-babel](https://github.com/rollup/plugins/tree/master/packages/babel)
- [rollup-plugin-filesize](https://github.com/ritz078/rollup-plugin-filesize)

**Babel:**
- [@babel/plugin-transform-runtime](https://babeljs.io/docs/en/babel-plugin-transform-runtime)
npm package: @harnessflex/uh-oh-dev
Description: A simple debugging tool for Harness Flex and Imba
Author: Mj Fold
Latest version: 0.0.5

# Uh-oh

`Uh-oh` is a modified version of [youch](https://github.com/poppinss/youch) for Harness Flex and Imba.

<br />

![Uh-oh!](screenshot.png)

<br />

Install
-------

This package is automatically installed with the Harness Flex Framework.

```
npm i @harnessflex/uh-oh
```

Usage
-----

```js
import { Middleware as errorHandler } from '@harnessflex/uh-oh'

express.use errorHandler!
```

And you're done!

> Note: `errorHandler` must be added at the end of your middleware list.

Credits
-------
A special thanks to the contributors of:

[stack-trace](https://github.com/felixge/node-stack-trace)

[youch](https://github.com/poppinss/youch)

[express-youch](https://github.com/hmil/express-youch)

See [Credits](CREDIT.md) for the complete list.

Security
-------

If you discover any security related issues, please email mjfold76@gmail.com instead of using the issue tracker.

License
-------

The MIT License (MIT). Please see [License File](LICENSE) for more information.
npm package: @harnessgg/electron
Description: CLI harness for AI agents to test Electron apps
Latest version: 0.1.0

# @harnessgg/electron

Lets AI agents test Electron apps through CLI commands and machine-readable JSON.

This package is agent-first (strict JSON output), with docs for both humans and LLMs.

- GitHub: https://github.com/harnessgg/electron
- Website: https://harness.gg

## Install

```bash
npm i -D @harnessgg/electron
```

Install as a development dependency so it is not part of production app installs.

## Prerequisite

Start your Electron app with a remote debugging port:

```bash
electron . --remote-debugging-port=9222
```

## Quick flow

```bash
harness-electron connect --port 9222
harness-electron dom --format summary
harness-electron type --css "input[type=email]" --value "user@example.com"
harness-electron click --role button --name "Sign in"
harness-electron assert --kind url --expected "/dashboard"
harness-electron screenshot --path "./artifacts/login.png"
harness-electron disconnect
```

`--session` defaults to `default`, so you only pass it when you need multiple concurrent sessions.

## JSON output examples

Success (`dom`):

```json
{
  "ok": true,
  "protocolVersion": "1.0",
  "command": "dom",
  "session": "default",
  "data": {
    "title": "BoostOS",
    "url": "http://localhost:5174/",
    "buttons": 100,
    "inputs": 0,
    "forms": 0
  }
}
```

Failure (`screenshot` timeout):

```json
{
  "ok": false,
  "protocolVersion": "1.0",
  "command": "screenshot",
  "session": "default",
  "error": {
    "code": "TIMEOUT",
    "message": "page.screenshot: Timeout 30000ms exceeded.",
    "retryable": true,
    "suggestedNext": [
      "harness-electron dom --format summary",
      "Retry command with a larger timeout"
    ],
    "details": {
      "source": "TimeoutError"
    }
  }
}
```

## Docs

- Human reference: `docs/human/commands.md`
- LLM quickstart: `docs/llm/quickstart.md`
- LLM command spec: `docs/llm/command-spec.md`
- LLM response schema: `docs/llm/response-schema.json`
- LLM error codes: `docs/llm/error-codes.md`