open-index/open-npm huggingface dataset:
npm package: @poa/core
Description: Poa — opinionated React framework
Latest version: 5.0.2

# Poa framework

[![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier)
[![lerna](https://img.shields.io/badge/maintained%20with-lerna-cc00ff.svg)](https://lernajs.io/)

Poa — opinionated React framework.

## Need framework documentation?

https://github.com/Strikersoft/poa

## Core

This is @poa/core package, that all users are installed. Since it is monorepo, you can find all dependecies here.
Core packange depends on all other packages. Primary responsibility — boot all plugins/system and provide public API.
npm package: @poa/i18n
Description: Poa — opinionated React framework
Latest version: 5.0.2

# Poa framework

[![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier)
[![lerna](https://img.shields.io/badge/maintained%20with-lerna-cc00ff.svg)](https://lernajs.io/)

Poa — opinionated React framework.

## Need framework documentation?

https://github.com/Strikersoft/poa

## i18n

This is @poa/i18n package. It is abstraction on top of i18next (https://github.com/i18next/i18next/)
Users should not directly install this package (only with @poa/core)
npm package: @poa/router
Description: Poa — opinionated React framework
Latest version: 5.0.2

# Poa framework

[![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier)
[![lerna](https://img.shields.io/badge/maintained%20with-lerna-cc00ff.svg)](https://lernajs.io/)

Poa — opinionated React framework.

## Need framework documentation?

https://github.com/Strikersoft/poa

## Route

This is @poa/route package. It is abstraction on top of mobx-little-router (https://github.com/mobx-little-router/mobx-little-router)
Users should not directly install this package (only with @poa/core)
npm package: @poa/satcheljs
Description: [![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier) [![lerna](https://img.shields.io/badge/maintained%20with-lerna-cc00ff.svg)](https://lernajs.io/)
Latest version: 5.0.2

# Poa framework

[![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier)
[![lerna](https://img.shields.io/badge/maintained%20with-lerna-cc00ff.svg)](https://lernajs.io/)

Poa — opinionated React framework.

## Need framework documentation?

https://github.com/Strikersoft/poa

## SatchelJS

This is @poa/satcheljs package. This is custom version of satcheljs (https://github.com/Microsoft/satcheljs) since there are global vision missunderstood (https://github.com/Microsoft/satcheljs/issues/90)
Users should not directly install this package (only with @poa/core)
npm package: @poa/state
Description: Poa — opinionated React framework
Latest version: 5.0.2

# Poa framework

[![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier)
[![lerna](https://img.shields.io/badge/maintained%20with-lerna-cc00ff.svg)](https://lernajs.io/)

Poa — opinionated React framework.

## Need framework documentation?

https://github.com/Strikersoft/poa

## State

This is @poa/state package. It is abstraction on top of satcheljs (https://github.com/Microsoft/satcheljs)
Users should not directly install this package (only with @poa/core)
npm package: @poach/core
Description: Helps transpiling, linting, and bundling node modules for the web.
Author: Marcello Montemagno
Latest version: 0.0.3

# Poach-core

The base [Poach](https://github.com/marcellomontemagno/poach) recipe.

This recipe configures the following tools

- [Webpack](https://webpack.js.org/)
- [ESlint](https://eslint.org/)
- [Babel](https://babeljs.io/)

in order to provide the following features

- Modern javascript.
- Code linting.
- Dev server with live reload.
- Ability to build your project as a static app.
- Ability to build your project as a [UMD](https://github.com/umdjs/umd).

We advise you get at least familiar with the mentioned tools before using this recipe.

# Setup

- Create a standard node module

```
mkdir your-project && cd $_ && npm init 
```

- Install `@poach/core` as a dev dependency of your project:

```
npm i --save-dev @poach/core
```
  
- Add the following to your `package.json`:

```
...
"main": "dist/umd/umd.js",
"scripts": {
    ...
    "build:app": "webpack --config webpack.app.js",
    "build:umd": "webpack --config webpack.umd.js",
    "build": "npm run build:app && npm run build:umd",
    "start": "webpack-dev-server --config webpack.dev.js"
    ...
},
...
```

- Copy the content of `node_modules/@poach/core/src/boilerplate` in the root folder of your project.

```
cp -R node_modules/@poach/core/boilerplate/ .
```

That's it, you can now use the following scripts:

- `npm run start` will start your application in development mode using `src/index.js` as entry point.
- `npm run build:app` will bundle your code as a static web application using `src/index.js` as entry point and `dist/app` as output directory.
- `npm run build:umd` will bundle your code as [UMD](https://github.com/umdjs/umd) using `src/module/index.js` as entry point and `dist/umd/umd.js` as output.
- `npm run build` will start `npm run build:app` and `npm run build:umd` one after the other.
 
# How is this different from a boilerplate project?

Notice that most of the files you just copied form `node_modules/@poach/core/src/boilerplate` don't do anything else but importing configuration form `@poach/core`.

Importing base configuration from `@poach/core` instead of just pasting it within your files is useful because it will give poach a chance to improve/upgrade the configuration when you upgrade the poach version in your package.json.

Copying files in your root directory is useful for the following reasons:

- Given that these files are in the root folder of your project your IDE will be able to use them automatically.
- You can use these files to customize the configuration coming from `@poach/core` if needed.

That's it, if you inspect your project there is nothing hidden from you, the project should have a simple and familiar structure.

# What's next 

Let's say you want to add [Typescript](https://www.typescriptlang.org/) and/or [React](https://github.com/facebook/react/) to your project you can simply install the related recipes. 

Recipes are available [here](https://github.com/marcellomontemagno/poach/tree/master/packages).
npm package: @poach/jest
Description: Poach configuration recipe for jest.
Author: Marcello Montemagno
Latest version: 0.0.3

# Poach-jest

[Poach](https://github.com/marcellomontemagno/poach) configuration recipe for [Jest](https://jestjs.io/).
  
Needs `@poach/core` and `@poach/react` installed and configured.

# Installation

`npm i --save-dev @poach/jest`

# Configuration

Extend your `.eslintrc.js`

```js
let config = require('@poach/core/config/eslint/eslint.core');
//...
config = require('@poach/react/config/eslint/eslint.core')(config); //you should already have this
config = require('@poach/jest/config/eslint/eslint.core')(config);
//...
module.exports = config;
```

- Copy the base `jest.config.js` in the root folder of your project.

```
cp -R node_modules/@poach/jest/boilerplate/jest.config.js .
```

- Add the following to your `package.json`:

```
...
"scripts": {
    ...
    "test": "jest"
    ...
},
...
```

You are now ready to write a [Jest](https://jestjs.io/) test anywhere in your project

```js
//example.test.js
it(`example test`, () => {
  expect(true).toBe(true)
})
```
npm package: @poach/react
Description: Poach configuration recipe for react.
Author: Marcello Montemagno
Latest version: 0.0.3

# Poach-react

[Poach](https://github.com/marcellomontemagno/poach) configuration recipe for [React](https://reactjs.org/).

Needs `@poach/core` installed and configured.

# Installation

`npm i --save-dev @poach/react`

# Configuration

Extend your `babel.config.js`

```js
let config = require('@poach/core/config/babel/babel.core');
//...
config = require('@poach/react/config/babel/babel.core')(config);
//...
module.exports = config;
```

Extend your `.eslintrc.js`

```js
let config = require('@poach/core/config/eslint/eslint.core');
//...
config = require('@poach/react/config/eslint/eslint.core')(config);
//...
module.exports = config;
```

Extend your `webpack.core.js`

```js
let config = require('@poach/core/config/webpack/webpack.core')
//...
config = require('@poach/react/config/webpack/webpack.core')(config);
//...
module.exports = config;
```

Render you first react component in `src/index.js`

```jsx
import React from 'react';
import ReactDOM from 'react-dom';

const div = document.createElement("div");
div.setAttribute("id", "react-root");
document.body.appendChild(div);

ReactDOM.render(<h1>React hello world!</h1>, div);
```
npm package: @poach/typescript
Description: Poach configuration recipe for typescript.
Author: Marcello Montemagno
Latest version: 0.0.3

# Poach-typescript

[Poach](https://github.com/marcellomontemagno/poach) configuration recipe for [Typescript](https://www.typescriptlang.org/).
  
Needs `@poach/core` installed and configured.

# Installation

`npm i --save-dev @poach/typescript`

# Configuration

Extend your `babel.config.js`

```js
let config = require('@poach/core/config/babel/babel.core');
//...
config = require('@poach/typescript/config/babel/babel.core')(config);
//...
module.exports = config;
```

Extend your `.eslintrc.js`

```js
let config = require('@poach/core/config/eslint/eslint.core');
//...
config = require('@poach/typescript/config/eslint/eslint.core')(config);
//...
module.exports = config;
```

Extend your `webpack.core.js`

```js
let config = require('@poach/core/config/webpack/webpack.core')
//...
config = require('@poach/typescript/config/webpack/webpack.core')(config);
//...
module.exports = config;
```

- Copy the base `tsconfig.json` in the root folder of your project.

```
cp -R node_modules/@poach/typescript/boilerplate/tsconfig.json .
```

You are now able to write `.ts` files in your project.
npm package: @poamslayer/ecfr
Description: CLI for the Electronic Code of Federal Regulations (eCFR) API
Latest version: 0.1.2

# ecfr

CLI for the [Electronic Code of Federal Regulations](https://www.ecfr.gov) (eCFR) API.

Search, browse, and read federal regulations from your terminal.

## Install

```bash
npm install -g ecfr
```

Or run directly:

```bash
npx ecfr titles
```

## Commands

### List all CFR titles

```bash
ecfr titles
```

### List agencies

```bash
ecfr agencies
ecfr agencies --filter defense
```

### Browse title structure

```bash
ecfr structure 32
ecfr structure 32 --date 2025-01-01
```

### Read regulation text

```bash
ecfr read 32 --part 2002 --section 2002.14
ecfr read 32 --part 2002 --xml          # raw XML output
ecfr read 48 --part 252 --date 2025-06-01
```

### Search regulations

```bash
ecfr search "controlled unclassified information"
ecfr search "cybersecurity" --title 32
ecfr search "CUI" --page 2 --per-page 5
```

### Search result counts

```bash
ecfr counts "cybersecurity"
ecfr counts "cybersecurity" --agency defense-department
```

### Track changes

```bash
ecfr changes 32 --since 2025-01-01
ecfr changes 48 --part 252
```

### View corrections

```bash
ecfr corrections
ecfr corrections --title 32
```

## Output modes

| Context | Output |
|---------|--------|
| Terminal (TTY) | Colored tables and formatted text |
| Piped (`\| jq`) | JSON |
| `--json` flag | JSON (always) |

## Requirements

Node.js 18+

## API

This tool wraps the public [eCFR API](https://www.ecfr.gov/developer/documentation/api/v1). No authentication required.

## License

MIT
npm package: @poamslayer/instantly-cli
Description: Zero-dependency CLI for the Instantly.ai v2 API
Author: Arnold De La Vega
Latest version: 0.1.0

# instantly-cli

Zero-dependency CLI for the [Instantly.ai](https://instantly.ai) v2 API. Manage campaigns, leads, analytics, email accounts, and inbox from the terminal.

## Install

```bash
npm install -g @poamslayer/instantly-cli
```

Requires Node.js 18+.

## Setup

Get your API key from [app.instantly.ai](https://app.instantly.ai/app/settings/integrations) → Settings → Integrations.

```bash
instantly config set-api-key <your-key>
```

Or set the `INSTANTLY_API_KEY` environment variable.

## Commands

### Campaigns

```bash
instantly campaigns list [--all] [--status 1] [--search "name"]
instantly campaigns get <id>
instantly campaigns create                # JSON stdin
instantly campaigns update <id>           # JSON stdin
instantly campaigns activate <id>
instantly campaigns pause <id>
instantly campaigns duplicate <id>
```

### Leads

```bash
instantly leads list --campaign <id> [--all] [--search "query"]
instantly leads get <id>
instantly leads add                       # JSON stdin (1-1000 leads)
instantly leads delete                    # JSON stdin
instantly leads update-status             # JSON stdin
```

### Analytics

```bash
instantly analytics campaign [--id <id>] [--start-date 2026-01-01] [--end-date 2026-12-31]
instantly analytics overview [--id <id>]
instantly analytics daily [--id <id>]
```

### Email Accounts

```bash
instantly accounts list [--all] [--status 1] [--search "email"]
instantly accounts test <email>           # Check SPF/DKIM/DMARC
```

### Inbox

```bash
instantly emails list [--campaign <id>] [--unread] [--type received]
instantly emails unread-count
```

### Config

```bash
instantly config set-api-key <key>
instantly config show
```

## Examples

**Add leads to a campaign:**

```bash
echo '{
  "campaign_id": "your-campaign-uuid",
  "leads": [
    {
      "email": "john@company.com",
      "first_name": "John",
      "last_name": "Smith",
      "company_name": "Acme Inc",
      "custom_variables": {
        "hook": "Saw your team is working on compliance...",
        "contract": "H9240323D0013"
      }
    }
  ]
}' | instantly leads add
```

Custom variables map to `{{hook}}`, `{{contract}}`, etc. in your Instantly email templates.

**Check campaign performance:**

```bash
instantly analytics campaign --id <campaign-id> | jq '{sent: .emails_sent_count, opened: .open_count, replied: .reply_count}'
```

**List active campaigns:**

```bash
instantly campaigns list --status 1
```

**Paginate through all results:**

```bash
instantly accounts list --all
```

## Auth Resolution

The API key is resolved in this order:

1. `--api-key` flag
2. `INSTANTLY_API_KEY` environment variable
3. `~/.instantly/config.json`

## Output

All commands output JSON to stdout. Errors go to stderr as JSON with a non-zero exit code. Pipe to `jq` for formatting or to other tools for processing.

## License

MIT
npm package: @poanet/solidity-flattener
Description: Combine solidity files to one flat file
Author: POA Network
Latest version: 3.0.9

# Solidity smart-contract flattened source file generation

[![Build Status](https://travis-ci.org/poanetwork/solidity-flattener.svg?branch=master)](https://travis-ci.org/poanetwork/solidity-flattener)
[![Known Vulnerabilities](https://snyk.io/test/github/poanetwork/solidity-flattener/badge.svg)](https://snyk.io/test/github/poanetwork/solidity-flattener)
[![Coverage Status](https://coveralls.io/repos/github/poanetwork/solidity-flattener/badge.svg?branch=master)](https://coveralls.io/github/poanetwork/solidity-flattener?branch=master)

## Utility to combine all imports to one flatten .sol file

### Installation from npm

`npm i @poanet/solidity-flattener`

### Usage

`./node_modules/.bin/poa-solidity-flattener ./contracts/example.sol`

It will save flattened source of Solidity smart-contract into `./out` directory

### Installation from source


```
git clone https://github.com/poanetwork/solidity-flattener
cd solidity-flattener
npm install
```

You can start script either

```
npm start "path_to_not_flat_contract_definition_file.sol"
```

or without paramaters (path to input file will be extracted from `./config.json`)

```
npm start
```



Expected result: 

```
Success! Flat file ORIGINAL_FILE_NAME_flat.sol is generated to ./out directory
```

`./flatContract.sol` - flat .sol file is created in output directory (`./out/` by default)

**Note:** *utility doesn't support aliases at import statements*

## Config

path `./config.json`

```
{
	"inputFilePath": "./demo/src/Oracles.sol",
	"outputDir": "./out"
}
```
npm package: @poap/poap-components
Description: Library of shared style and components.
Author: Ruben
Latest version: 0.1.31

# @poap/poap-components
@poap/poap-components is a collection of reusable styles and components for building POAP specific applications. The library includes a variety of components such as text, buttons, forms, and layouts with the latest POAP style.

Hosted examples: https://poap-xyz.github.io/poap-components/

## Requirements
* Core-js (if using Vite)

## Installation
You can install @poap/poap-components via npm:

```
npm install @poap/poap-components
```

## Usage
You can use components like this

```
import { Button } from '@poap/poap-components'

function MyPage() {
    return (
        <Button>Click me!</Button>
    )
}
```

## Making changes
To start using this library, first run the following command to install the necessary dependencies:

```
npm i
```
Once the installation is complete, run the following command to start the development server:

```
npm start
```
This will start a local instance of Storybook, where you can view and interact with the library's components.

To sumbit a change:

- [ ] edit the components in the `src/components` folder
- [ ] increment the version number in `package.json`
- [ ] commit and push your feature branch

### Modifying Components/Modules
If you need to make changes to a component, navigate to the relevant file in `src/components/` and modify or add it as needed. Take a look in the `Button` folder for file and folder structure.

Note: When adding or exporting new components, make sure to do so in the appropriate `index.js` file.

### Creating Stories
If new components are created make sure to also create a story to showcase it in Storybook. To do this, create a new story file in the component folder and use the title tag to properly add the story to the right section, heading, or chapter. For example:

```
export default {
  title: 'Form fields/Atoms/Button',
  component: Button,
};
```

This will add the Button component to the "Form fields" section, under the "Atoms" heading.

Once you have created your story, it will automatically be added to the Storybook UI, where you can view it and make sure it is working as intended.
npm package: @poap/sane-data
Description: A collection of data validations and sanetisers
Author: Mentor
Latest version: 0.0.7

# POAP Data validations and sanetisers

This [npm package](https://www.npmjs.com/package/@poap/sane-data) contains a number of regex-based validations as well as string sanetisers that are common in POAP-related dApps.

You can view the complete list of included elements and their documentation here here:

- [View all regex validations](https://github.com/poap-xyz/sane-data/tree/main/src/modules/validations.js)
- [View all sanitisation functions](https://github.com/poap-xyz/sane-data/tree/main/src/modules/sanitisers.js)

## Usage

To use this package, install it by running `npm i -S @poap/sane-data` and using either the regexes or the sanetiser functions.

Example sanetiser usage:

```js
// Import the sanetisers you need
import { sanetise_eth_address, sanetise_ens_address, sanetise_eth_or_ens_address, sanetise_poap_id, sanetise_poap_edit_code, sanetise_email, sanetise_string } from '@poap/sane-data'

// Use the sanetisers in your code
function send_poap( wallet_or_ens, drop_id, email ){

    try {

        // Sanetise the data
        wallet_or_ens = sanetise_eth_or_ens_address( wallet_or_ens )
        drop_id = sanetise_poap_id( drop_id )

        // Sanetisers throw by default, if you want to continue even when the sanetiser fails, you can disable throwing like so:
        email = sanetise_email( email, false )

        // Then do whatever you want to do
        ...

        return { success: true }

    } catch( e ) {

        // The thrown error can be due to invalid values
        console.error( `Error doing things:`, e )
        return { error: e.message }

    }

}

```

Example regex usage:

```js

// Import the regexes you need
import { eth_address_regex, ens_regex, eth_or_ens_address_regex, email_regex, poap_id_regex, poap_edit_code_regex } from '@poap/sane-data'

// Use the regexes
const user_address = `0x0000000000000000000000000000000000000000`
if( user_address.match( eth_address_regex ) ) return 'You qualify for the airdrop'

```
npm package: @poap/skunk-linter
Description: Linting and styleguide for team skunk
Author: Mentor
Latest version: 0.0.3

# ESLint declarations for team skunk

A shared set of standards and preferences, enforced through eslint and vscode.

## Quickstart

To use:

1. `npm install -D @poap/skunk-linter @babel/eslint-parser eslint eslint-plugin-react husky`
1. Copy `.eslintrc.js` to your project's `.eslintrc.js`
1. Copy `.babelrc` to your project's `.babelrc`
1. Copy `.vscode/settings.json` to your project's `.vscode/settings.json`
1. Copy `.husky/pre-commit` to your project's `.husky/pre-commit`
1. Run husky initial setup

Lazy shell

```shell
npm install -D @poap/skunk-linter @babel/eslint-parser eslint eslint-plugin-react husky
mkdir .vscode .husky

# Download files
curl https://raw.githubusercontent.com/poap-xyz/skunk-linter/main/.eslintrc.js --output .eslintrc.js
curl https://raw.githubusercontent.com/poap-xyz/skunk-linter/main/.vscode/settings.json --output .vscode/settings.json
curl https://raw.githubusercontent.com/poap-xyz/skunk-linter/main/.husky/pre-commit --output .husky/pre-commit
curl https://raw.githubusercontent.com/poap-xyz/skunk-linter/main/.babelrc --output .babelrc
git add -f .eslintrc.js .babelrc .vscode/* .husky/*
chmod ug+x .husky/*
npm pkg set scripts.prepare="husky install"
npm pkg set scripts.lint="eslint --fix src"
npm run prepare
npx husky add .husky/pre-commit
git add .husky/pre-commit
```

## Making changes

The relevant source files are in `modules/`. If you make a change, you can update the package by:

1. Making the changes
1. Updating the version number in `package.json`
1. Pushing to the main branch of the repo or opening a pull request