open-index/open-npm huggingface dataset:
npm package: @orbio/orbio-openclaw
Description: Official Orbio OpenClaw plugin for Brazilian B2B account discovery, lead generation, and chat-based exports.
Latest version: 0.1.0

# Orbio OpenClaw Plugin (official)

Official OpenClaw plugin for Orbio account discovery, lead generation, and export workflows.

Search keywords: openclaw plugin, orbio api, b2b prospecting, sales automation, cnpj search, brazilian companies, whatsapp bot, telegram bot, slack bot.
Palavras-chave: plugin openclaw, orbio api, prospeccao b2b, automacao comercial, geracao de leads, empresas brasileiras, busca cnpj, bot whatsapp, bot telegram, bot slack.

Machine-readable summary for agent crawlers: `llms.txt`.

## Package

- npm package: `@orbio/orbio-openclaw`
- plugin id: `orbio-openclaw`

## What it provides

- `orbio_search`: chat-safe account search.
- `orbio_export`: export job creation (`csv`/`html`).
- `orbio_export_status`: export status polling.
- `orbio_command`: command dispatcher used by `/orbio ...` skill.

## Security posture

- No `exec`, `curl`, or subprocess execution.
- Workspace-scoped API key authentication (`Authorization: Bearer <api_key>`).
- Structured execution-context telemetry header (`X-Orbio-Execution-Context`) for integration/channel attribution.
- Contact data masked by default.
- Plugin-side request throttling (`maxRequestsPerMinute`) in addition to server-side limits.
- Retries only for transient failures (timeouts and 5xx), never for 4xx.

## Required configuration

- `baseUrl`: Orbio API base URL (for example, `https://api.orbioapi.com.br`)
- `apiKey`: Orbio API key for the workspace

Optional:

- `workspaceId` (default: `default`)
- `channel` (default: `chat`)
- `sendExecutionContext` (default: `true`)
- `timeoutMs` (default: `20000`)
- `maxRequestsPerMinute` (default: `30`)
- `retryCount` (default: `1`)
- `retryBackoffMs` (default: `300`)
- `capabilitiesTtlMs` (default: `60000`)

## Development

```bash
pnpm install --frozen-lockfile
pnpm lint
pnpm typecheck
pnpm test
pnpm coverage
pnpm verify
```

Coverage policy: minimum `95%` for lines, branches, functions, and statements.

## Live smoke (real environment)

```bash
export ORBIO_BASE_URL="https://api.orbioapi.com.br"
export ORBIO_API_KEY="<sandbox_key>"
export ORBIO_WORKSPACE_ID="openclaw-smoke"
export ORBIO_SMOKE_QUERY="empresas de desenvolvimento de software em sao paulo"
pnpm smoke:live
```

Reference env file: `.env.smoke.example`

## Release checklist

1. Bump version in `package.json`.
2. Sync version in `openclaw.plugin.json`.
3. Sync `PLUGIN_VERSION` in `src/index.ts`.
4. Run `pnpm verify` and `pnpm pack --dry-run`.
5. Publish with `pnpm publish --access public --no-git-checks --provenance`.
npm package: @orbionchain/orbionfinance-sdk
Description: 🛠 An SDK for building multichain swap applications on top of Orbion Finance.
Latest version: 2.2.2

# OrbionFinance SDK

[![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier)
[![npm](https://img.shields.io/npm/v/@orbionchain%2Forbionfinance-sdk)](https://www.npmjs.com/package/@orbionchain/orbionfinance-sdk)
[![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg)](https://prettier.io)

> ⚡ OrbionFinance SDK is a TypeScript library for building DEX and DeFi applications powered by OrbionChain across multiple EVM-compatible blockchains such as Ethereum, BSC, Sepolia, and beyond.

---

## ✨ Features

- 🧮 Precise math with [`JSBI`](https://github.com/GoogleChrome/jsbi) and [`big.js`](https://github.com/MikeMcl/big.js)
- 🔁 Multichain support with chain-aware factory/router/config resolution
- ⚖️ Fractional arithmetic: `Price`, `Percent`, `TokenAmount`, `CurrencyAmount`
- 💸 Supports native assets (`ETH`, `BNB`, etc.) via wrapping abstraction
- 🧩 Modular structure: clean separation of entities, fractions, and core utilities

---

## 📦 Installation

```bash
npm install @orbionchain/orbionfinance-sdk
# or
yarn add @orbionchain/orbionfinance-sdk
npm package: @orbis-cascade/oca-central-package
Description: Orbis Cascade Alliance primo-explore central package.
Author: Primo Customization Standing Group
Latest version: 1.1.0

# Orbis Cascade Alliance primo central package
[![npm version](https://img.shields.io/npm/v/primo-explore-send-sms.svg)](https://www.npmjs.com/package/primo-explore-send-sms)
## contents

| customization | description | repository |
|-|-|-|
| toggle institutions | allows the list of summit borrowing institutions to be collapsed & expanded | [primo-explore-toggle-institutions](https://github.com/alliance-pcsg/primo-explore-custom-actions) |
<!-- | custom resource icons | adds a set of resource icons from the noun project to search results | [primo-explore-resource-icons](https://github.com/alliance-pcsg/primo-explore-resource-icons) | -->

## installation

see the [releases page for the repository](https://github.com/alliance-pcsg/oca-central-package/releases) to download `CENTRAL_PACKAGE.zip`. this file can be uploaded to the Primo Back Office customization manager.

## developing

**you'll need the latest versions of docker and docker-compose.**

the development environment has two parts:

- the central package code, located in `src`
- a generic view package called ALLIANCE, located in `test`

here's how to use them:
1. start a development server with `npm start`.
2. results will be visible at [http://localhost:8003/primo-explore/search?vid=ALLIANCE](http://localhost:8003/primo-explore/search?vid=ALLIANCE)
3. you can edit the code in the `src` folder to change the central package and the dev environment will automatically generate `src/js/custom.js`.
4. if you install customization packages using npm, they will automatically be added to `src/js/custom.js`.
5. to test inheritance, you can also edit the code in the `test/ALLIANCE` folder as if you were developing that view. it will automatically refresh.
6. when finished, you can use `ctrl+c` to quit the dev environment and docker will clean up the container.

## building

when you're finished making changes:
1. run `npm run create-package` and choose `CENTRAL_PACKAGE` at the prompt.
2. a `CENTRAL_PACKAGE.zip` file will appear in `dist` (likely overwriting the previous one).
3. consider [bumping the version number](https://docs.npmjs.com/cli/version) using `npm version`.
4. if you cut a new release, consider uploading the `CENTRAL_PACKAGE.zip` file as a [build artifact](https://github.com/blog/1547-release-your-software) of the github release.
npm package: @orbis-cascade/primo-explore-force-services-page-auth
Description: force non-logged-in primo-explore users to authenticate when they are redirected to the services page.
Author: Nick Budak
Latest version: 1.1.0

# primo-explore-force-services-page-auth

<!-- ![Build Status](https://api.travis-ci.org/Alliance-PCJWG/primo-explore-clickable-logo.svg?branch=master) -->

## Features
When users are directed to the services page (e.g. from a database) and are not already logged in, Primo will trigger a login. This should work for both PDS and non-PDS authentication.

## Install
1. Make sure you've installed and configured [primo-explore-devenv](https://github.com/ExLibrisGroup/primo-explore-devenv).
2. Navigate to your template/central package root directory. For example:
    ```
    cd primo-explore/custom/MY_VIEW_ID
    ```
3. If you do not already have a `package.json` file in this directory, create one:
    ```
    npm init -y
    ```
4. Install this package:
    ```
    npm install primo-explore-force-services-page-auth --save-dev
    ```

## Usage
Once this package is installed, add `forceServicesPageAuth` as a dependency for your custom module definition.

```js
var app = angular.module('viewCustom', ['forceServicesPageAuth'])
```
Note: If you're using the `--browserify` build option, you will need to first import the module with:

```javascript
import 'forceServicesPageAuth';
```

<!-- ## Running tests
1. Clone the repo
2. Run `npm install`
3. Run `npm test` -->
npm package: @orbis-cascade/primo-explore-login-backgrounds
Description: Adds rotating background images to primo's standalone login screen.
Author: Nick Budak
Latest version: 1.1.0

# primo-explore-login-backgrounds

![Build Status](https://api.travis-ci.org/alliance-pcsg/primo-explore-login-backgrounds.svg)
[![npm](https://img.shields.io/npm/v/primo-explore-login-backgrounds.svg)](https://www.npmjs.com/package/primo-explore-login-backgrounds)

## Features
Full-screen background images appear on the standalone login page when a user navigates to `/primo-explore/login`. Images can be included with the view package in a `login` subfolder and enumerated in a config option. A new image is randomly chosen from the configured options each time the page is visited.

### Screenshot
![screenshot](screenshot.png)

## Install
1. Make sure you've installed and configured [primo-explore-devenv](https://github.com/ExLibrisGroup/primo-explore-devenv).
2. Navigate to your template/central package root directory. For example:
```
cd primo-explore/custom/MY_VIEW_ID
```
3. If you do not already have a `package.json` file in this directory, create one:
```
npm init -y
```
4. Install this package:
```
npm install primo-explore-login-backgrounds --save-dev
```

## Usage
Once this package is installed, add `loginBackgrounds` as a dependency for your custom module definition.

```js
var app = angular.module('viewCustom', ['loginBackgrounds'])
```
Note: If you're using the `--browserify` build option, you will need to first import the module with:

```javascript
import 'primo-explore-login-backgrounds';
```
You can set up the images by adding them to a new folder `login` inside the `img` directory of your view package. When you have finished adding images, you can add a configuration block like the one below listing the ones you wish to make available.

### Example

The example below adds three images, one of which will be randomly chosen each time a user logs in. We assume `lib1.jpg`, `lib2.jpg`, and `lib3.jpg` all reside in `MY_VIEW/img/login`.

```js
app.constant('loginImages', [
  'lib1.jpg',
  'lib2.jpg',
  'lib3.jpg'
])
```

## Running tests
1. Clone the repo
2. Run `npm install`
3. Run `npm test`
npm package: @orbis-cascade/primo-explore-oadoi-link
Description: Provides link to Open Access content for articles in primo-explore full display, when available.
Author: Jeremy McWilliams
Latest version: 1.0.1

# primo-explore-oadoi-link
Provides link to Open Access content for articles, when available

## Features
In a full display record, checks for the presence of a DOI. Queries the [OADOI API (v2)](https://oadoi.org/api/v2), and upon the presence of an open access link, displays a bar with the link under the "View It" section.

### Screenshot
![screenshot](screenshot.png)

## Install
1. Make sure you've installed and configured [primo-explore-devenv](https://github.com/ExLibrisGroup/primo-explore-devenv).
2. Navigate to your template/central package root directory. For example:
    ```
    cd primo-explore/custom/MY_VIEW_ID
    ```
3. If you do not already have a `package.json` file in this directory, create one:
    ```
    npm init -y
    ```
4. Install this package:
    ```
    npm install primo-explore-oadoi-link --save-dev
    ```

## Usage
Once this package is installed, add `oadoi` as a dependency for your custom module definition.

```js
var app = angular.module('viewCustom', ['oadoi'])
```

Note: If you're using the `--browserify` build option, you will need to first import the module with:

```javascript
import 'primo-explore-oadoi-link';
```

You can configure the banner by passing a configuration object. All properties are required.

| name      | type         | usage                                                                                   |
|-----------|--------------|-----------------------------------------------------------------------------------------|
| `imagePath` | string       | icon for next to the image link                                               |
| `email` | string       | email address attached to api query                                               |

The code below adds a banner similar to the above image.

```js
app.constant('oadoiOptions', {
  "imagePath": "custom/LCC/img/oa_50.png",
  "email": "youremail@domain.com"
})
```

<!-- ## Running tests
1. Clone the repo
2. Run `npm install`
3. Run `npm test` -->
npm package: @orbis-cascade/primo-explore-report-problem
Description: adds a "report a problem" banner to the detail view of an item in primo-explore.
Author: Nick Budak
Latest version: 3.1.0

# primo-explore-report-problem

[![npm](https://img.shields.io/npm/v/primo-explore-report-problem.svg)](https://www.npmjs.com/package/primo-explore-report-problem)

## Features
A banner with a link to report a problem/bug appears below the "send to" actions in the details view. The text of the banner is configurable, and clicking the button will redirect to an external URL and pass the parameters of the current search to that URL. This can be used to auto-fill an external "report problem" form.

### Screenshot
![screenshot](screenshot.png)

## Install
1. Make sure you've installed and configured [primo-explore-devenv](https://github.com/ExLibrisGroup/primo-explore-devenv).
2. Navigate to your template/central package root directory. For example:
    ```
    cd primo-explore/custom/MY_VIEW_ID
    ```
3. If you do not already have a `package.json` file in this directory, create one:
    ```
    npm init -y
    ```
4. Install this package:
    ```
    npm install primo-explore-report-problem
    ```

alternatively, just copy `dist/module.js` into your package's `custom.js` file.

## Usage
Once this package is installed, add `reportProblem` as a dependency for your custom module definition.

```js
var app = angular.module('viewCustom', ['reportProblem'])
```

Then, enable the customization by embedding it in the `prmActionListAfter` hook:
```js
app.component('prmActionListAfter', {template: '<oca-report-problem />'})
```

#### Configuration
You can configure the banner by passing in attributes to the `oca-report-problem` element. The `report-url` property is required; the others will default to the values shown in the screenshot.

| name      | type         | usage                                                                                   |
|-----------|--------------|-----------------------------------------------------------------------------------------|
| `message-text` | string       | banner text displayed next to the button.                                               |
| `button-text`  | string       | text displayed on the button itself.                                                    |
| `report-url`    | string (url) | base URL for your 'report a problem' page, to which all of the search parameters will be sent |

The line below would add a banner with different button and message texts.

```js
app.component('prmActionListAfter', {template: '<oca-report-problem report-url="http://my.library.edu/reportproblem.php?" message-text="Want to report a problem?" button-text="Submit report" />'})
```

When the button is clicked, if the user was viewing a page like: `https://primo.lclark.edu/primo-explore/fulldisplay?docid=CP71139633100001451&context=L&vid=......`

They would be sent to:
`http://my.library.edu/reportproblem.php?docid=CP71139633100001451&context=L&vid=.....`

All of the URL parameters could then be handled by a server-side script.

## Running tests
1. Clone the repo
2. Run `npm install`
3. Run `npm test`