open-index/open-npm huggingface dataset:
npm package: @superoutcast/n8n-nodes-abacusai-chat
Description: n8n node for AbacusAI chat integration
Author: SuperOutcast
Latest version: 1.0.21

# n8n AbacusAI Chat Node

This is a custom n8n node that integrates with AbacusAI to enable chat functionality with AI models.

## Installation

1. Clone or download this repository.
2. Run `npm install` to install dependencies.
3. Run `npm run build` to compile the TypeScript code.
4. Copy the `dist` folder to your n8n custom nodes directory.
5. Restart n8n.

## Usage

1. In n8n, add the "AbacusAI Chat" node to your workflow.
2. Configure your AbacusAI credentials:
   - Go to Credentials in n8n.
   - Create new credentials of type "AbacusAI Credentials".
   - Enter your AbacusAI API key.
3. In the node properties:
   - **Message**: The text message to send to the AI model.
   - **Deployment Name**: The name of your AbacusAI deployment.
   - **Temperature**: Controls randomness (0-1, default 0.7).
   - **Max Tokens**: Maximum tokens to generate (default 1000).
4. Connect the node to your workflow and run it.

## Output

The node outputs a JSON object with:
- `response`: The AI's chat response.
- `deploymentName`: The deployment used.
- `temperature`: The temperature setting used.
- `maxTokens`: The max tokens setting used.

## Requirements

- n8n instance
- AbacusAI API key
- Deployed chat model in AbacusAI

## API Reference

This node uses the AbacusAI v0 predict API endpoint. Make sure your deployment supports chat inputs.

For more information, visit [AbacusAI Documentation](https://docs.abacus.ai/).
npm package: @superpackages/telebot
Description: A framework for easily building push-button Telegram bots. From the simplest to the most complex.
Author: dortanes
Latest version: 1.0.5

# 🤖 Telebot

**The declarative framework for building push-button Telegram bots with ease.**

Telebot is designed for developers who want to build complex, menu-driven Telegram bots without the boilerplate. It provides a fluent, declarative API for menus, automatic navigation, and streamlined conversations.

[![NPM Version](https://img.shields.io/npm/v/@superpackages/telebot.svg)](https://www.npmjs.com/package/@superpackages/telebot)
[![License](https://img.shields.io/npm/l/@superpackages/telebot.svg)](LICENSE)

## ✨ Features

- 🏗️ **Declarative Menus**: Define your bot's layout using a fluent builder API.
- 🔄 **Automatic Navigation**: Nested menus with built-in "Back" buttons.
- 💬 **Linear Conversations**: Collect user input easily with `ask()` and `form()`.
- 📝 **Single-Message Flow**: Edits the same message during interaction for a clean chat history.
- 🔡 **Type-Safe**: Written in TypeScript with full JSDoc documentation.
- 🌐 **Localization Support**: Built-in hooks for i18n.
- 🛠️ **Powered by Grammy**: Leverages the speed and reliability of the `grammy` framework.

## 🚀 Quick Start

### 1. Install

```bash
npm install @superpackages/telebot grammy
```

### 2. Create your bot

```typescript
import { Telebot } from "@superpackages/telebot";

// Define an action
const greetAction = Telebot.action(async ({ ctx, conversation }) => {
  const name = await conversation.ask("What is your name?");
  await ctx.reply(`Hello, ${name}! Welcome to the bot.`);
});

// Define a menu
const mainMenu = Telebot.menu((layout) => {
  layout.text("Main Menu");
  layout.button("Say Hello").action(greetAction);
  layout.button("External Link").url("https://github.com/dortanes/telebot");
});

// Start the bot
const bot = Telebot.create({
  token: "YOUR_BOT_TOKEN",
  menu: mainMenu,
});

bot.start();
```

## 📖 Documentation

Explore the detailed guides:

- [Menus and Navigation](docs/menus.md) - Building layouts, rows, and buttons.
- [Conversations and Forms](docs/conversations.md) - Collecting user input and complex data.
- [Actions and Triggers](docs/actions.md) - Logic, commands, and regex triggers.
- [State Management](docs/state.md) - Sessions, storage, and user resolution.
- [Advanced Patterns](docs/advanced.md) - I18n, custom storage, and manual rendering.

## 🤝 Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

## 📜 License

[MIT](LICENSE)
npm package: @superpixeldx/nesnes
Description: New EcmaScript NES emulator
Author: Koen Kivits
Latest version: 0.3.1

# NESNES

NESNES (New EcmaScript NES) is a pure JS NES emulator. Try the [demo](http://koen.kivits.com/nesnes)!

[![NESNES screenshot](http://koen.kivits.com/nesnes/screenshot.png)](http://koen.kivits.com/nesnes)

## Installation

NESNES can be installed through npm:

```
npm install nesnes
```

## Getting started

NESNES can be used as follows:

```js
var NesNes = require("nesnes");

var emulator = new NesNes( canvas );
emulator.load( pathToRom, callback );
```

These are the parameters being used:
   * ``canvas``: a &lt;canvas&gt; DOM object to which the video output will be rendered. Not required (though nothing will be rendered if no canvas is given).
   * ``pathToRom``: the path to an INES rom file (most ROMs found on the internet are in this format)
   * ``callback``: function to be executed once the ROM has been loaded and initialized. If ``true`` is passed instead of a function the ROM will automatically start playing once it has been loaded.

## Build standalone

If you're running NESNES in the browser and don't want to use Browserify for your page, you can build a standalone version:

```
npm install
make
```

This will create ``nesnes.js`` in ``dist/``, which exposes a global NesNes object when included in your web page. Note that this file also comes packaged with the npm module.

## Configuration

Default configuration (keyboard and gamepad input) can be found in ``config.json``. Input can also be configured programmatically:

```js
// configure the first player controller to use the gamepad
emulator.input.configure(0, "gamepad", {
	"buttons": {
		"0": "b",
		"1": "a",
		"8": "select",
		"9": "start"
	},
	"axes": {
		"0": "horizontal", // map axis 0 to left/right
		"1": "vertical", // map axis 1 to up/down
	}
})
```

See ``config.json`` for an example configuration.

Note that multiple input types can be enabled for a single controller. For example, a single controller can listen to both the keyboard and a gamepad.

## Testing

NESNES includes a basic test server. You can run it by executing:

```
bin/nesnes-server
```

from a directory containing NES ROMs. This starts up an HTTP server at localhost, serving only a simple page containing a NESNES instance and a ROM selection input to be able to test games. NESNES is recompiled on every page load to make it easy to see how your changes affect the emulator.

A lot of third party test ROMs are included in the ``test`` directory to debug specific parts of the emulator.

## My game doesn't work!

Please file an issue or send a pull request. :)
npm package: @superqjq/message
Description: A message component for Vue.js
Author: superqjq
Latest version: 0.0.4

# A Simple Message Tip Component for Vue.js

## Installation
```
npm i -S @superqjq/message
```

## Usage
In `main.js` of a Vue Project:
```javascript
import message from '@superqjq/toast';
Vue.use(message);
```

In any Vue component, you can simply use `this.$message()` to popup a tip:
```javascript
<script>
export default {
  mounted() {
    this.$message({
      type: 'info',
      title: '提示',
      message: '三国演义'
    });

    // or 
    this.$message.error('重生')
  }
}
</script>
```

## Options and Defaults
### type
*string*  
Default value is `success`.  
Type of message, could be one of these values: `success` | `warning` | `error` | `info`.

### title
*string*  
The info you want to show on the message title. (should be short)

### message
*string*
The info you want to show on the message.

### duration
*number*  
Default value is `3`.  
How many seconds he message should be shown, after that it could disapear automaticly.  
Specially, you can set a value of `-1`, which means showing the message forever.

### showFooter
*Boolean*  
Default value is `false`.  
Whether to display asynchronous execution buttons

### confirmText  cancelText
*string*  
Text prompt

### confirmStyle cancelStyle
*Boolean*
Default value is `false`
Button color

## Example
```javascript
  this.$message({
    type: 'info',
    title: '提示',
    message: '三国演义',
    showFooter: true,
    confirmText: '取消',
    cancelText: '确定',
    confirmStyle: true,
    cancelStyle: true
  }).then(() => {
    console.log(1111)
    /* dosomething */
  }, () => {
    console.log(2222)
    /* dosomething */
  })
```
npm package: @superqjq/toast
Description: A toast component for Vue.js
Latest version: 0.0.3

# A Simple Popup Tip Component for Vue.js

## Installation
```
npm i -S @champyin/toast
```

## Usage
In `main.js` of a Vue Project:
```javascript
import toast from '@champyin/toast';
Vue.use(toast);
```

In any Vue component, you can simply use `this.$toast()` to popup a tip:
```javascript
<script>
export default {
  mounted() {
    this.$toast({
      type: 'success',
      msg: 'Bravo!'
    });
  }
}
</script>
```

## Options and Defaults
### type
*string*  
Default value is `success`.  
Type of toast, could be one of these values: `success` | `warning` | `danger` | `loading`.

### msg
*string*  
The info you want to show on the toast. (should be short)

### duration
*number*  
Default value is `3`.  
How many seconds he toast should be shown, after that it could disapear automaticly.  
Specially, you can set a value of `-1`, which means showing the toast forever.

### position
*string*  
Default value is `top-center`.  
Position of toast, could be one of these values: `top-left` | `top-center` | `top-right` | `bottom-left` | `bottom-center` | `bottom-right` | `center-center`.

### fullWith
*boolean*  
Default value is `false`.  
Determines the toast appears in a full-with way or not.


## Example
```javascript
this.$toast({
  type: 'warning',
  msg: 'Caution!',
  duration: 6,
  position: 'top-center'
});
```
npm package: @superrb/gatsby-addons
Description: Addons for use with Gatsby + Prismic sites
Author: James Dinsdale
Latest version: 8.1.5

# Gatsby Addons

## Installation

First, install the package

```sh
yarn add @superrb/gatsby-addons
```

## Package aliases

Add the following webpack aliases in `gatsby-node.ts`.

```tsx
export const onCreateWebpackConfig = async ({ actions }) => {
  actions.setWebpackConfig({
    resolve: {
      alias: {
        ProjectRoot: path.resolve(__dirname, '.'),
        '@superrb/gatsby-addons-cms': path.resolve(
          './node_modules/@superrb/gatsby-addons-prismic/', // Replace with path to chosen CMS extension
        ),
      },
    },
  })
}
```

## Context Providers

Add the context providers in `src/gatsby-browser.tsx` and `src/gatsby-ssr.tsx` for any of the [contexts](./src/context/README.md) you wish to use.

```tsx
import { LazyLoadingContextProvider, NavContextProvider, TranslationContextProvider } from '@superrb/gatbsy-addons/context'

export const wrapRootElement = ({ element }) => (
  <LazyLoadingContextProvider>
    <NavContextProvider>
      <TranslationContextProvider>
        {element}
      </TranslationContextProvider>
    </NavContextProvider>
  </LazyLoadingContextProvider>
)
```

## Language Map

If you want to use translations, after adding the translation context provider, create a language map for each language you want to use in `src/utils/translation.ts`.

Example:

```ts
import en from '../translations/en.json'
import jp from '../translations/jp.json'

export type Messages = Partial<typeof en & typeof jp>

export enum Language {
  en = 'en', // These strings should match the language or locale code used in Prismic
  jp = 'jp',
}

const translations = (
  language: Language = process.env.GATSBY_LANGUAGE as Language,
) => {
  switch (language) {
    case Language.jp:
      return jp as Messages
    case Language.en:
      return en as Messages
    default:
      return en as Messages
  }
}

export default translations
```

Translations should be stored in `src/translations/<lang>.json`. The typescript types are automatically generated based on the keys in the JSON file.

## Image Reverse Proxy

To use a reverse proxy for Images you can replace the domain in the image urls by populating the following env vars:

```env
GATSBY_IMAGE_URL_FIND="images.prismic.io"
GATSBY_IMAGE_URL_REPLACE="reverseproxy.cdn.com"
```

All image URLs will be converted from `https://images.prismic.io/image.webp` to `https://reverseproxy.cdn.com/image.webp`

## Further Documentation
* [Components](./src/components/README.md)
* [Contexts](./src/context/README.md)
* [Hooks](./src/hooks/README.md)
* [Utilities](./src/utils/README.md)
npm package: @superrb/gatsby-plugin-multi-language-sitemap
Description: Gatsby plugin that automatically creates a sitemap supporting multi-language for your site
Latest version: 1.1.4

# 💎Gatsby-plugin-multi-language-sitemap 

Create a sitemap for your Gatsby site.

The plugin is a fork of [gatsby-plugin-sitemap](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-sitemap) . This forked version has support multiple languages support, designed for aftership. 

### 🧸How to use it?

##### 1.create a gatsby project

```bash
gatsby new demo
cd demo
```

##### 2. install package

```bash
# npm
npm i gatsby-plugin-multi-language-sitemap
# yarn
yarn add gatsby-plugin-multi-language-sitemap
```

##### 3. config sitemap plugin at `gatsby-config.js`

```js
module.exports = {
  plugins: [
    {
      resolve: `gatsby-plugin-multi-language-sitemap`,
      options: {
        output: '/',
        query: `
          query {
            allSitePage {
              nodes {
                path
              }
            }
            site {
              siteMetadata {
                siteUrl
              }
            }
          }
        `,
        langs: ['en', 'de', 'fr', 'es', 'zh-Hant', 'zh-Hans'],
      },
    }
  ]
}
```

The plugin distinguish the language by the url prefix. 

For example, if your url like below format. The sitemap plugin will take effect.

```
https://gatsbystarterdefaultsource.gatsbyjs.io/app
https://gatsbystarterdefaultsource.gatsbyjs.io/en/app
https://gatsbystarterdefaultsource.gatsbyjs.io/fr/app
https://gatsbystarterdefaultsource.gatsbyjs.io/zh-Hans/app
https://gatsbystarterdefaultsource.gatsbyjs.io/jp/app
```

and the langs param will be

```js
langs: ['en', 'fr', 'zh-Hans', 'jp']
```

##### 4. run commands below, you can see the sitemap in `/public/` folder, `sitemap-index.xml` `x-default-sitemap.xml` screenshot below.

```bash
yarn build
```

![image-20210715142625438](https://raw.githubusercontent.com/SteveYuOWO/gatsby-plugin-multi-language-sitemap/main/screenshot/1.png)

![image-20210715142851589](https://raw.githubusercontent.com/SteveYuOWO/gatsby-plugin-multi-language-sitemap/main/screenshot/2.png)  

##### 5. compat `gatsby-plugin-sitemap` , you can use more native features at below link

https://www.gatsbyjs.com/plugins/gatsby-plugin-sitemap/
npm package: @superrb/kunstmaan-addons-messaging-service
Description: Messaging service for use on Kunstmaan front end
Author: @molovo
Latest version: 1.0.2

# Kunstmaan Addons Messaging Service

A simple service to allow notification-style messaging on the front end of Kunstmaan CMS websites.

## Installation

```sh
yarn add @superrb/kunstmaan-addons-messaging-service
```

## Usage

Add the HTML container somewhere on the page. This will pull messages from Symfony's session flashbag

```html
<ul id="messages" class="messages" data-turbolinks-permanent>
  {% for type, messages in flash %}
    {% for message in messages %}
      <li class="message message--{{ type }}" {% if type != 'error' %}data-timeout="5000"{% endif %}>
        <span class="message__text">
          {{ message | trans }}
        </span>

        <button class="message__close">
          <span class="screenreader-text">Close message</span>
        </button>
      </li>
    {% endfor %}
  {% endfor %}
</ul>
```

The `data-timeout` attribute sets a time in ms after which the message will disappear.

### Creating messages

```js
import messagingService from '@superrb/kunstmaan-addons-messaging-service'

// Persistent messages
messagingService.info('This a message')
messagingService.error('This is an error message')
messagingService.warning('This is a warning message')
messagingService.success('This is a success message')

// Auto-hide message after 5 seconds
messagingService.info('This message will hide after 5 seconds', 5000)

// Close all visible messages (handy to call on `turbolinks:visit`)
messagingService.closeAll()
```

## Authors

- James Dinsdale ([@molovo](https://github.com/molovo))

## License

- Details on the license [can be found here](LICENSE.md)
npm package: @superrb/netlify-function-helpers
Description: Helper methods for writing Netlify functions
Author: James Dinsdale
Latest version: 1.1.0

# Netlify Function Helpers

A library of helpers to use when writing Netlify functions.

## `withCors`

A wrapper around the netlify function callback to handle CORS and parse posted data.

#### Usage

```
const { withCors, ValidationError } = require('@superrb/netlify-function-helpers')

exports.handler = withCors((data) => {
  // Throw `ValidationError` to respond with an error message and a 400 status code
  if (!data) {
    throw new ValidationError('Missing data')
  }

  // Throw any other error to respond with the error message and a 500 status code
  try {
    doSomething()
  } catch (err) {
    throw new Error('Something went wrong')
  }

  // Return an object, which will be sent to the client as JSON
  return {
    success: true
  }
})
```
npm package: @superreal/octopus
Description: Recursive and multi-threaded broken link checker
Author: superReal GmbH
Latest version: 1.3.0
Deprecated: This package has been moved to @deptagency/octopus

<p align="center">
    <img src="https://raw.githubusercontent.com/superReal/octopus/master/octopus.png" width="128" height="128" alt="Octopus">
    <br>
    <b>Octopus</b>
    <br>
    Quickly crawl a whole website for broken links
</p>


### Install

```bash
npm install --global @superreal/octopus
```

*or*

```bash
yarn global add @superreal/octopus
```


### Usage

```bash
octopus <domain> [options]
```


### Options

Option | Description | Default
------ | ----------- | -------
`--ignore-query` | Ignore a query string | `false`
`--ignore-external` | Ignore all external links | `false`
`--ignore-nofollow` | Ignore `rel=nofollow` links | `false`
`--slack-webhook` | Slack incoming webhook url | `none`
`--timeout` | Time to wait for response | `5000`
`--silent` | Run without printing progress line | `false`
`--help` | Output help text |  


### Examples

```bash
octopus www.superreal.de
octopus www.awg-mode.de --ignore-external
octopus www.hardeck.de --ignore-query=isEnergyEfficiencyChartOpen --ignore-query=followSearch
octopus www.golfino.com --silent --slack-webhook=https://hooks.slack.com/services/XXX/XXX/XXX
```


### Icon
Made by [Freepik](https://www.freepik.com) from [www.flaticon.com](https://www.flaticon.com)
npm package: @superreal/srgrid
Description: Dead Simple Flexbox Grid
Author: superReal GmbH
Latest version: 1.0.1

# sR Grid
> Dead Simple Flexbox Grid

[![Dependency Status](https://david-dm.org/superReal/srgrid.svg)](https://david-dm.org/superReal/srgrid)
[![devDependencies Status](https://david-dm.org/superreal/srgrid/dev-status.svg)](https://david-dm.org/superreal/srgrid?type=dev)
[![Code Climate](https://codeclimate.com/github/superReal/srgrid/badges/gpa.svg)](https://codeclimate.com/github/superReal/srgrid)
[![Build Status](https://travis-ci.org/superReal/srgrid.svg?branch=master)](https://travis-ci.org/superReal/srgrid)
[![Known Vulnerabilities](https://snyk.io/test/github/superReal/srgrid/badge.svg)](https://snyk.io/test/github/superReal/srgrid)

sR Grid is a flexible and fully responsive grid system based on [Flexbox](https://www.w3.org/TR/css-flexbox-1/).
It follows the mobile first approach and the [features](/docs/features/README.md) are module-based. In the default setup each feature is disabled 
and can be enabled as required. In this way the generated code remains as small as possible.

The sR Grid uses data attributes. The markup remains clear and easy to understand.


## Installation
     
```bash
$ yarn add @superreal/srbreakpoints @superreal/srgrid
```

If you prefer using npm:

```bash
$ npm install --save @superreal/srbreakpoints @superreal/srgrid
```

*Note: the sR Grid module uses [sR Breakpoints](https://github.com/superreal/srbreakpoints) as a dependency.*


## Usage

1. Import the sR Breakpoints & sR Grid modules
2. [Init sR Breakpoints](https://github.com/superreal/srbreakpoints#usage) module
3. Create a sR Grid grid

```scss
@import 'path_to_node_modules_folder/@superreal/srbreakpoints/src/styles/srbreakpoints.scss';
@import 'path_to_node_modules_folder/@superreal/srgrid/src/styles/srgrid.scss';

@include srbreakpoints-init(
 // Your sR Breakpoints settings
);
@include srgrid-create-grid(
 // Your sR Grid settings
);
```

## Browser compatibility

### Desktop
| Chrome | Firefox | Safari | Opera | EDGE | Internet Explorer |
|:------:|:-------:|:------:|:-----:|:----:|:-----------------:|
| 29     | 28      | 9      | 17    | 12   | 11                |

### Mobile
| Chrome for Android | iOS Safari | Android Browser | Samsung Internet |
|:------------------:|:----------:|:---------------:|:----------------:|
| 57                 | 9.2        | 4.4             | 4                |


## Documentation
* [Settings](https://superreal.github.io/srgrid/docs/settings)
* [Helpers](https://superreal.github.io/srgrid/docs/helpers)
* [Features](https://superreal.github.io/srgrid/docs/features/)
* [Advanced](https://superreal.github.io/srgrid/docs/advanced)


## License (MIT)
Copyright (c) [superReal GmbH](http://www.superreal.de)
npm package: @supersaasapp/uikit
Description: shopify ui components library wrapper
Author: kohia
Latest version: 1.0.2

# superops-kit

> superops ui components library

[![NPM](https://img.shields.io/npm/v/superops-kit.svg)](https://www.npmjs.com/package/superops-kit) [![JavaScript Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://standardjs.com)

## Install

```bash
npm install --save superops-kit
```

## Usage

```tsx
import React, { Component } from 'react'

import MyComponent from 'superops-kit'
import 'superops-kit/dist/index.css'

class Example extends Component {
  render() {
    return <MyComponent />
  }
}
```

## License

MIT © [kohia](https://github.com/kohia)
npm package: @supersafe/mcp
Description: SuperSafe MCP server — scan URLs for security vulnerabilities from Claude Code
Latest version: 0.2.4

# @supersafe/mcp

MCP server for scanning URLs for security vulnerabilities. Works with Claude Code, Cursor, Windsurf, and any MCP-compatible AI tool.

**No signup required** -- just add it and start scanning.

## Setup

### Claude Code

Add to your project config (`.mcp.json`):

```json
{
  "mcpServers": {
    "supersafe": {
      "command": "npx",
      "args": ["@supersafe/mcp"]
    }
  }
}
```

Or add it globally in `~/.claude.json`:

```json
{
  "mcpServers": {
    "supersafe": {
      "command": "npx",
      "args": ["@supersafe/mcp"]
    }
  }
}
```

Restart Claude Code after adding the config.

### Cursor / Windsurf

Add the same config to your editor's MCP settings. Refer to your editor's docs for the config file location.

## Tools

| Tool | Description |
|------|-------------|
| `scan_url` | Scan a URL for security vulnerabilities (SAFE mode, passive checks) |
| `get_findings` | Get findings for a scan by job_id |
| `get_remediation` | Get fix guidance for a finding type |
| `get_scan_diff` | Compare a scan to the previous scan on the same target |
| `login` | Authenticate via browser -- upgrades anonymous to persistent scans |
| `whoami` | Check your current identity and auth method |

## Usage

Once set up, just ask your AI tool:

> "Scan example.com for security issues"

Results include severity, evidence, remediation steps, and an `agent_prompt` field your AI can use to help you fix each finding.

## Authentication

### Anonymous (default)

Works out of the box. Scans are rate-limited (10 per 15 minutes) and not persisted to an account.

### Browser login (recommended)

Ask your AI tool to log in:

> "Log in to SuperSafe"

This opens your browser where you can sign up or log in. Your session is stored locally at `~/.supersafe/mcp-tokens.json` and persists across restarts -- no config changes needed.

### API Key

For CI/CD or headless environments, set your API key:

```json
{
  "mcpServers": {
    "supersafe": {
      "command": "npx",
      "args": ["@supersafe/mcp"],
      "env": {
        "SUPERSAFE_API_KEY": "your-api-key"
      }
    }
  }
}
```

## Environment Variables

| Variable | Description | Default |
|----------|-------------|---------|
| `SUPERSAFE_API_KEY` | API key for authenticated access | _(anonymous)_ |
| `SUPERSAFE_URL` | API base URL | `https://supersafe.dev` |

## Requirements

Node.js >= 22

## License

MIT