open-index/open-npm huggingface dataset:
npm package: @mastergo/html-mastergo
Description: Convert HTML to Mastergo code
Author: Mastergo
Latest version: 1.10.0

# html-mastergo

[中文](./README.zh-CN.md) | **English**

A library can convert html into MasterGo plugin data structures.
## Install

```shell
yarn add @mastergo/html-mastergo | npm install @mastergo/html-mastergo
```

## Usage

1. Install [MasterGo client](https://mastergo.com/resource) and init a plugin project.

2. Build [UI](https://developers.mastergo.com/guide/setup.html#%E6%9E%84%E5%BB%BA%E7%94%A8%E6%88%B7%E7%95%8C%E9%9D%A2)(Click here [MasterGo-Plugin](https://developers.mastergo.com/) if having trouble in how to develop plugins in MasterGo)

3. Use the library

   ```typescript
   /** UI side **/
   import { htmlToMG, postProcess } from '@mastergo/html-mastergo';
   // any dom element
   const convert = async () => {
     const layerJson = await htmlToMG(document.body);
     // Not necessary, you can do anything you want to do with json processed by the function htmlToMG. This is just one way to do it.
     const processedJson = await postProcess(layerJson)
     // post data to plugin
     parent.postMessage({
       type: 'generate',
       data: processedJson
     }, '*')
   }
   
   
   /** Plugin side **/
   import { renderToMasterGo } from '@mastergo/html-mastergo';
   mg.ui.onmessage = (msg) => {
     const { data, type } = msg
     if (type === 'generate') {
       // traverse
       renderToMasterGo(data).then(root => {
         console.log('root node', root)
       })
     }
   }
   ```

## Limitations

A few known limitations:

- Not all element types are supported (e.g. iframes)
- Not all CSS properties are supported or fully supported
- Not all types of media are supported (video, animated gifs, etc)
- All fonts must be uploaded to MasterGo, otherwise the default fonts will be used for rendering

If you find any problems or have any feedback, please [Ask a Question](https://github.com/mastergo-design/html-to-mastergo/issues/new)

## Example

[Example](./src/example/html-mg)
npm package: @mastergo/plugin-utils
Description: **本项目为MasterGo插件API的ts声明文件。**
Latest version: 0.7.0

# MasterGO Plugin Utils 

**本项目为MasterGo插件API的ts声明文件。**

##This repository is no longer supported, please use [mastergo/plugin-typings](https://www.npmjs.com/package/@mastergo/plugin-typings) instead.

##此项目不再维护,请您迁移至 [mastergo/plugin-typings](https://www.npmjs.com/package/@mastergo/plugin-typings).
npm package: @mastermart/formio-custom-components
Description: Contrib components for form.io
Author: Mastermart
Latest version: 1.0.12

Voor de readme van het originele project zie https://github.com/formio/contrib. 

Stappen om custom component toe te voegen+draaiend te krijgen:

BUILDER

- Clone de formio.js SDK (https://github.com/formio/formio.js/) en zoek een component uit die zoveel mogelijk lijkt op dat wat je wilt gaan maken
- Zet alles voor jouw component uit de SDK uit /components en /templates in src/components en src/templates. Lib hoef je niet aan te passen. 
- Doe aanpassingen

- Als je je aanpassingen wilt testen, draai npm install
- Pak de formio-contrib.use.min.js uit /dist, upload deze en neem de link naar de url. Ik heb dropbox gebruikt, dan krijg je dit soort linkjes https://dl.dropboxusercontent.com/s/f1zyeg266auul43/formio-contrib.use.min.js?dl=0. 
Je mag niet naar een download link verwijzen, de link moet direct naar de het javascript bestand verwijzen. 
- Open de form io management tool (https://portal.form.io/) en zet de link onder settings/Custom js and css, klik opslaan en herlaad de pagina, klik 'ok'
- Doe hetzelfde voor de .css als je daar aanpassingen in gedaan hebt (src/sass/contrib.css, deze wordt gecompileerd naar dist/contrib.css).
- Rinse and repeat tot het werkt

------------------------------------------------------------------------------------------------------
RENDERER

- De renderer https://bitbucket.org/yourrequest/form-renderer/src/master/ heeft een dependency op dit project. 
Als je je wijzigingen in de renderer wilt zien moet je deze pushen in dit project en npm install draaien op de renderer
- Als je een nieuwe custom component toegevoegd hebt: voeg deze toe in de renderer aan app.component.ts:initializeApp() zoals dat al gedaan wordt voor slider.
npm package: @mastermart/nijmegen-custom-components
Description: Contrib components for form.io
Author: Mart van den Broek
Latest version: 1.10.0

Voor de readme van het originele project zie https://github.com/formio/contrib. 

Stappen om custom component toe te voegen+draaiend te krijgen:

BUILDER

- Clone de formio.js SDK (https://github.com/formio/formio.js/) en zoek een component uit die zoveel mogelijk lijkt op dat wat je wilt gaan maken
- Zet alles voor jouw component uit de SDK uit /components en /templates in src/components en src/templates. Lib hoef je niet aan te passen. 
- Doe aanpassingen

- Als je je aanpassingen wilt testen, draai npm install
- Pak de formio-contrib.use.min.js uit /dist, upload deze en neem de link naar de url. Ik heb dropbox gebruikt, dan krijg je dit soort linkjes https://dl.dropboxusercontent.com/s/f1zyeg266auul43/formio-contrib.use.min.js?dl=0. 
Je mag niet naar een download link verwijzen, de link moet direct naar de het javascript bestand verwijzen. 
- Open de form io management tool (https://portal.form.io/) en zet de link onder settings/Custom js and css, klik opslaan en herlaad de pagina, klik 'ok'
- Doe hetzelfde voor de .css als je daar aanpassingen in gedaan hebt (src/sass/contrib.css, deze wordt gecompileerd naar dist/contrib.css).
(Als je alleen Nijmegen componenten aan het nabouwen bent kun je hier ook de css van Nijmegen neerzetten: https://componenten.nijmegen.nl/v5.0.1/nijmegen.css)
- Rinse and repeat tot het werkt

------------------------------------------------------------------------------------------------------
RENDERER

- De renderer https://bitbucket.org/yourrequest/form-renderer/src/master/ heeft een dependency op dit project. 
Als je je wijzigingen in de renderer wilt zien moet je deze pushen in dit project en npm install draaien op de renderer
- Als je een nieuwe custom component toegevoegd hebt: voeg deze toe in de renderer aan app.component.ts:initializeApp() zoals dat al gedaan wordt voor slider. 
- Styling hoef je in principe niets voor te doen als je Nijmegen componenten aan het nabouwen bent, de Nijmegen css is al onderdeel van dit project.
npm package: @mastermindzh/eslint-config
Description: My default eslint config
Author: Mastermindzh
Latest version: 3.1.0

# eslint-config

My personal (base) eslint-config

## Table of Contents

<!-- toc -->

- [install](#install)
- [usage](#usage)

<!-- tocstop -->

## install

```sh
npm install --save-dev @mastermindzh/eslint-config
```

## usage

Extend it in your eslint config:

```json
{
  "extends": "@mastermindzh/eslint-config"
}
```
npm package: @mastermunj/eslint-config
Description: The base configuration for ESLint used by my packages
Author: Munjal Dhamecha
Latest version: 0.0.2

# @mastermunj/eslint-config

[![npm version](https://img.shields.io/npm/v/@mastermunj/eslint-config.svg)](https://www.npmjs.com/package/@mastermunj/eslint-config)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

The base ESLint configuration used across my TypeScript packages.

## Features

* [TypeScript ESLint](https://typescript-eslint.io/) for TypeScript linting
* [Prettier](https://prettier.io/) integration for code formatting
* [ESLint Stylistic](https://eslint.style/) for stylistic rules
* [ESLint Plugin Unicorn](https://github.com/sindresorhus/eslint-plugin-unicorn) for opinionated best practices
* Strict error rules for common JavaScript pitfalls
* Consistent naming conventions and code style

## Installation

```sh
npm install --save-dev @mastermunj/eslint-config eslint prettier
```

## Usage

Create an `eslint.config.js` file in your project root:

```javascript
import { configPkg } from '@mastermunj/eslint-config';

export default configPkg();
```

### Custom Configuration

You can extend the base configuration with your own rules:

```javascript
import { configPkg } from '@mastermunj/eslint-config';

export default configPkg(
  {
    rules: {
      // Your custom rules here
    },
  }
);
```

### Using Exported Constants

The package also exports useful constants that you can use:

```javascript
import {
  configPkg,
  INCLUDE_LIST,
  GLOBAL_IGNORE_LIST,
  PLUGINS_LIST,
  RULES_LIST,
} from '@mastermunj/eslint-config';

export default configPkg(
  {
    files: ['**/*.js'],
    rules: {
      // Override specific rules
    },
  }
);
```

## Scripts

Add these scripts to your `package.json`:

```json
{
  "scripts": {
    "lint": "eslint .",
    "lint:fix": "eslint . --fix"
  }
}
```

## License

[MIT](LICENSE)
npm package: @mastermunj/oxc-config
Description: Shared oxlint + oxfmt configuration for TypeScript packages
Author: Munjal Dhamecha
Latest version: 0.0.4

# @mastermunj/oxc-config

Shared Oxlint and Oxfmt configuration for TypeScript packages.

## What this package provides

- Shareable `oxlint` base config
- Shareable `oxfmt` base config
- A simple starting point that teams can customize per package

## Install

```sh
npm install --save-dev @mastermunj/oxc-config oxlint oxfmt oxlint-tsgolint@latest
```

## Usage

### 1) Oxlint config

Create `.oxlintrc.json` in your project root:

```json
{
  "extends": ["./node_modules/@mastermunj/oxc-config/.oxlintrc.json"]
}
```

### 2) Customize lint rules on top

Yes, you can both override existing rules and add new rules.

Example:

```json
{
  "extends": ["./node_modules/@mastermunj/oxc-config/.oxlintrc.json"],
  "rules": {
    "typescript/no-explicit-any": "warn",
    "no-console": "error"
  },
  "overrides": [
    {
      "files": ["scripts/**/*.ts"],
      "rules": {
        "eslint/no-console": "off"
      }
    }
  ]
}
```

### 3) Oxfmt config

Use the shared formatter config via `--config`:

```sh
oxfmt --check --config ./node_modules/@mastermunj/oxc-config/.oxfmtrc.json .
oxfmt --write --config ./node_modules/@mastermunj/oxc-config/.oxfmtrc.json .
```

### 4) Scripts

```json
{
  "scripts": {
    "lint": "oxlint --type-aware .",
    "lint:fix": "npm run lint -- --fix",
    "format": "oxfmt --check --config ./node_modules/@mastermunj/oxc-config/.oxfmtrc.json .",
    "format:fix": "oxfmt --write --config ./node_modules/@mastermunj/oxc-config/.oxfmtrc.json ."
  }
}
```

### 5) Customize formatter settings

`oxfmt` does not currently support deep config inheritance like lint `extends` in the same way.

Recommended approach:

- Start from the shared config file
- Copy into your package as `.oxfmtrc.json`
- Adjust only settings you want to change

## Package Exports

- `@mastermunj/oxc-config/oxlint`
- `@mastermunj/oxc-config/oxfmt`

## License

MIT
npm package: @masterodin/chilipiper-concierge
Description: Chili Piper Concierge
Latest version: 1.1.89

# Concierge JS

This is a fork of [`@chilipiper/concierge`](https://www.npmjs.com/package/@chilipiper/concierge),
with all dev dependencies removed, as they were generating peer dependency warnings.

For more information on usage, see:

- https://help.chilipiper.com/hc/en-us/sections/8297706662931-Form-Concierge
- https://help.chilipiper.com/hc/en-us/sections/4413992693139-Other-Form-Concierge-Implementations
- https://help.chilipiper.com/hc/en-us/articles/360053799073
npm package: @masterodin/eslint-config-javascript
Description: Shareable eslint config for JavaScript projects
Author: Matthew Peveler
Latest version: 2.0.1

# @masterodin/eslint-config-javascript

[![npm (scoped)](https://img.shields.io/npm/v/@masterodin/eslint-config-javascript)](https://npmjs.com/package/@masterodin/eslint-config-javascript)

Shareable eslint config for javascript projects. This extends off of the `eslint:recommended` ruleset with a bunch of additional style stuff.

## Installation

npm install @masterodin/eslint-config-javascript

## Usage

Edit your `eslint` config file to then extend off of `@masterodin/eslint-config-javascript`. You do not need to include `eslint:recommended`.
npm package: @masterodin/eslint-config-typescript
Description: [![npm (scoped)](https://img.shields.io/npm/v/@masterodin/eslint-config-typescript)](https://npmjs.com/package/@masterodin/eslint-config-typescript)
Author: Matthew Peveler
Latest version: 3.1.1

# @masterodin/eslint-config-typescript

[![npm (scoped)](https://img.shields.io/npm/v/@masterodin/eslint-config-typescript)](https://npmjs.com/package/@masterodin/eslint-config-typescript)

Shareable eslint config for typescript projects.

## Installation

```bash
npm install --save-dev @masterodin/eslint-config-typescript @typescript-eslint/parser @typescript-eslint/eslint-plugin
```

## Usage

Alter your eslintrc file to have:

```json
{
    "extends": [
        "@masterodin/eslint-config-typescript"
    ]
}
```
npm package: @masterodin/recall-ai-bot-sdk
Description: SDK for building with recall.ai bots
Author: MasterOdin
Latest version: 0.0.1

# Recall.ai Bot SDK

A TypeScript SDK for building with [Recall.ai](https://www.recall.ai/) bots.

## Installation

```bash
npm install @masterodin/recall-ai-bot-sdk
```

## Basic Usage

```typescript
import { RecallAi } from '@masterodin/recall-ai-bot-sdk';

const client = new RecallAi({
  apiKey: '...', // can omit and get value from process.env.RECALL_AI_API_KEY
  region: 'us-east-1'
});

await client.listBots();
```
npm package: @masterportal/masterportalapi
Description: Basic functions of the Masterportal as api
Author: Implementierungspartnerschaft Masterportal
Latest version: 2.60.0

# masterportalapi

The masterportalAPI is an API to include and show map-content on your webpage. It's based on OpenLayers and extended with functions to easily use configuration and infrastructure files from the masterportal, a feature-rich mapping app developed by geowerkstatt hamburg. It also provides the creation of a 3d map by using olcs and cesium. Check masterportal.org for further information.

## Usage

Install the masterportalAPI in your project with ``npm install masterportalapi``. The project does not have a default export, but various named exports. Generate and check the documentation as described below for details.

If you want to create a 3d map, you have to provide the peer dependency cesium.

By importing the project by module name like ``import ... from "masterportalAPI"``, most bundlers and bundler configurations will include the whole masterportalAPI. If you only need a subset of the provided functions and want to keep your build clean, directly import the needed functions like ``import {createMap} from "masterportalAPI/src/map.js``.

## Error Handling

1. Error event callback: The methods `createMap` and `addLayer` both optionally accept error event callbacks that are called with OpenLayers error events (tileloaderror, imageloaderror, featuresloaderror, error).
2. Ping: A method that returns a Promise. This resolves to the status code of the layer's GetCapabilities request, which can be used to decide if the service is reachable and usable at all.

Both methods may be required for useful user feedback. For example, a WMS may answer a tile request with 404 if no tile is available for a region, but may be fully available within its specification. This may throw an error while the service itself is available as specified. It is up to the using implementation how to react, how often to ping, and so on.

## Scripts

|Script|Effect|
|-|-|
|``npm run example``|Starts a dev server with a running example. Please mind that the page seen is _not_ part of the masterportalAPI, but merely an environment for manual testing. Change code within ``./example/index.js`` to try things. Free hot reloading thanks to parcel.|
|``npm run generate-jsdoc``|Generates the project documentation within the folder ``./docs``.|
|``npm test``|Runs all tests. Prints code coverage to console.|
|``npm run test:watch``|Runs all tests in watch mode. Good practive to let this run during development in a separate terminal. |

## About Babel

The Babel dev dependencies are purely added for development tests and jest tests. Babel is required for testing since Node does not support ES6 in .js files so far.
npm package: @mastersign/jupyterlab_sublime
Description: Sublime notebook cell binding for JupyterLab
Author: Tobias Kiertscher
Latest version: 0.1.0

# jupyterlab_sublime

[![npm version](https://badge.fury.io/js/%40mastersign%2Fjupyterlab_sublime.svg)](https://badge.fury.io/js/%40mastersign%2Fjupyterlab_sublime)
[![npm downloads](https://img.shields.io/npm/dw/%40mastersign%2Fjupyterlab_sublime.svg)](https://badge.fury.io/js/%40mastersign%2Fjupyterlab_sublime)

> This is a tailored fork of [ryantam626/jupyterlab_sublime](https://github.com/ryantam626/jupyterlab_sublime).

A slightly opinionated Sublime notebook cell binding for JupyterLab.

## Notes

Most of the keybindings implemented by CodeMirror just work out of the box after switching the key map, there were a little pesky keys that collide either with my system level shortcuts, broswer shortcuts or jupyterlab shortcuts.
A few keybindings which seem most useful are adapted.
Consult the [checklist](sublimeKeyChecklist.md) for more details.

## Why opinionated?

There are some keybindings which simply don't feel useful, so they are repurposed, again see the [checklist](https://github.com/mastersign/jupyterlab_sublime/blob/master/sublimeKeyChecklist.md).

## Prerequisites

* JupyterLab 1.0

## Installation

```bash
jupyter labextension install @mastersign/jupyterlab_sublime
```

## Development

For a development install (requires npm version 4 or later), do the following in the repository directory:

```bash
npm install
jupyter labextension link .
```

To rebuild the package and the JupyterLab app:

```bash
jupyter lab build
```
npm package: @mastersof-ai/dark-factory
Description: An automated software engineering tool with 100% AI engineers. Built on Claude Code.
Author: Masters of AI
Latest version: 0.1.1

# Dark Factory — Deprecated

> **This project has been deprecated.** Its successor is [@mastersof-ai/harness](https://github.com/mastersof-ai/harness), a multi-agent runtime built on the [Claude Agent SDK](https://docs.anthropic.com/en/docs/claude-agent-sdk).

Dark Factory took a skills/prompt approach — markdown files that Claude Code interprets as workflows. With Claude Opus 4.6, that's no longer the right abstraction. The agentic approach in `@mastersof-ai/harness` is more capable, more flexible, and where all future development is happening.

## Migration

```bash
# Uninstall Dark Factory
npx @mastersof-ai/dark-factory uninstall

# Install the harness
npm install -g @mastersof-ai/harness
```

See the [harness README](https://github.com/mastersof-ai/harness#readme) for setup instructions.

## License

MIT — see [LICENSE](LICENSE)
npm package: @mastertanzeel/safe-run
Description: Run untrusted Node.js projects with safer defaults, transparent risk prompts, and sandboxed execution.
Latest version: 1.0.0

# safe-run

Run untrusted Node.js projects with safer defaults, transparent prompts, and sandboxed execution.

## Why safe-run?

`safe-run` is built for developers who need to inspect and run unknown repositories without blindly executing dependency scripts.

It focuses on:

- Zero-trust install flow
- Explicit user consent for risky actions
- Human-readable risk insights
- Least-privilege Docker sandboxing

## Install

```bash
npm i -g @mastertanzeel/safe-run
```

Or run directly:

```bash
npx @mastertanzeel/safe-run dev
```

## Modes

### 1) Dev mode (default low-friction)

```bash
safe-run dev
```

What it does:

- Runs `npm install --ignore-scripts`
- Runs `npm audit --json`
- Detects suspicious dependency install scripts
- Prompts before running risky scripts (default: no)
- Prompts before running your command (`npm run dev` by default)

### 2) Sandbox mode (Docker isolation)

```bash
safe-run sandbox
```

What it does:

- Runs in Docker
- Uses non-root user
- Uses `no-new-privileges`
- Drops Linux capabilities
- Uses `--network none` by default

### 3) Freelance mode (high security)

```bash
safe-run freelance
```

What it does:

- Safe install with scripts blocked
- Strict script approvals (default deny)
- Hardened Docker sandbox
- Restricted environment passthrough (no secret env injection)

## Prompt Example

```text
⚠️ Package "xyz" wants to run install scripts.
This may be dangerous.
Allow execution? (yes/no, default: no)
```

## Suspicious Script Detection

safe-run flags patterns such as:

- `curl` or `wget`
- Piping to shell (`| bash`, `| sh`)
- Remote URL downloads
- Base64 decode + execute patterns
- `eval` / `new Function`

## Optional External Scans

safe-run includes:

- `npm audit` (MVP, built-in)
- Optional OSV.dev query batch
- Optional Socket.dev lookups (API key prompt with hidden input)

Security behavior:

- API keys are prompted via hidden input
- Keys are kept in-memory only
- Keys are never logged or stored to disk

## Network Monitoring (Best Effort)

Use `--monitor-network` in Docker modes to print basic socket activity from inside container.

```bash
safe-run sandbox --monitor-network
```

## CLI Help

```bash
safe-run --help
```

## Development

```bash
npm install
npm run lint
node index.js --help
```

## Security Principles

- Zero trust for external code
- Explicit consent for risky actions
- Least privilege by default
- No hidden behavior

## License

MIT