open-index/open-npm huggingface dataset:
npm package: @ingeni/igs-vault
Description: A CLI tool to fetch secrets from HashiCorp Vault and write to .env files
Author: Your Name
Latest version: 1.5.0

## developper:

```bash
npm run build
chmod +x dist/index.js
npm link
igs-vault --help
```

## how to use

```bash
# setup
igs-vault setup
igs-vault setup-script url username password
# Example
# igs-vault setup-script http://127.0.0.1:8200 admin admin

# init: create igs-vault.json with vault path mappings
igs-vault init .env
# interactive: select root → select sub → saves to igs-vault.json
# example output:
# [{"path": "secret/data/develop/data/test01", "env": ".env"}]

# write env: copy key value from vault then write a file
igs-vault write development/data/your-env .env
# or without arguments (reads from igs-vault.json)
igs-vault write

# read
igs-vault read development/data/your-env

# set key value
igs-vault setkv development/data/your-env key value

# update from env file
igs-vault updatekv development/data/your-env .env.local
# or use path ending with '/' to select from list
igs-vault updatekv development/ .env.local
# or without arguments (reads from igs-vault.json)
igs-vault updatekv

# updatekv behavior:
# - key exists in vault path → update
# - key not in vault path but exists in /global/prod/windows with different value → warn and update
# - key not in vault path and not in global → prompt to add (Yes/No)

# append
# append/change values from vault to .env file
igs-vault append development/data/your-env .env
# or use path ending with '/' to select from list
igs-vault append development/ .env
# or without arguments (reads from igs-vault.json)
igs-vault append
```

## igs-vault.json

When using `init`, `write`, or `append`, paths are saved to `igs-vault.json` in the current directory.
This allows running `append`, `write`, or `updatekv` without arguments — it will prompt you to select from saved paths.

```json
[
  { "path": "secret/data/develop/data/test01", "env": ".env" },
  { "path": "secret/data/stag/data/test01", "env": ".env.staging" }
]
```
npm package: @ingeni/igsdbclient
Description: ## MSSQL [Example](https://github.com/ingeni-team/DBConnectCLient/blob/main/src/__test__/mssql.test.ts) ## ORACLE [Example](https://github.com/ingeni-team/DBConnectCLient/blob/main/src/__test__/oracle.test.ts)
Latest version: 1.0.0

# `IGS Db Client`

## MSSQL
[Example](https://github.com/ingeni-team/DBConnectCLient/blob/main/src/__test__/mssql.test.ts)
## ORACLE
[Example](https://github.com/ingeni-team/DBConnectCLient/blob/main/src/__test__/oracle.test.ts)
npm package: @ingenious-agency/react-scripts
Description: Ingenious Configuration and scripts for Create React App.
Latest version: 1.0.17-2

# react-scripts

This package includes custom configuration of the scripts used by [Create React App](https://github.com/facebookincubator/create-react-app).<br>
Please refer to its documentation:

* [Getting Started](https://github.com/facebookincubator/create-react-app/blob/master/README.md#getting-started) – How to create a new app.
* [User Guide](https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md) – How to develop apps bootstrapped with Create React App.

## Usage

You can use this scripts with the normal [create-react-app](https://www.npmjs.com/package/create-react-app), just adding the parameter `scripts-version` to point to this project.

```bash
$ create-react-app <app-name> --scripts-version @ingenious-agency/react-scripts
```
npm package: @ingenious-redox/destination-middleware
Description: A set of expressjs middlewares to ease the development of Redox destinations endpoints
Author: Gabriel Chertok
Latest version: 0.3.0

# Redox Destination Utils

This package is a collection of express middleware functions that helps building Redox destination apps with node and express.

When you set up a Redox destination, this means an endpoint that listens to requests from the Redox engine you need to do the following:

1. First respond to a challenge that redox engine sends to verify that you own the server the redox engine will be calling
2. Verify on each request that the caller is redox
3. Handle in a particular way each message type you can receive

## `answerChallenge(req, res)`

The `answerChallenge` middleware will return to Redox engine the challenge sent by in the request with a status of `200`.

```js
const express = require("express");
const { answerChallenge } = require("@ingenious-redox/destination-middleware");
const app = express();

app.get("/", answerChallenge); // Use `app.get` when the challenge is configured with GET for your destination on Redox engine UI

app.listen(process.env.PORT, () =>
  console.log(`Example app listening on port ${process.env.PORT}!`)
);
```

## `verifyCaller(verificationToken) => (req, res)`

```js
const express = require("express");
const { answerChallenge } = require("@ingenious-redox/destination-middleware");
const app = express();

app.use(verifyCaller(process.env.VERIFICATION_TOKEN)); // This verification token should match the one that's configured for your destination on Redox engine UI

app.listen(process.env.PORT, () =>
  console.log(`Example app listening on port ${process.env.PORT}!`)
);
```

The `verifyCaller` middleware is configured with the verification token and returns a middleware in charge of validating the correct header.

## `routeMessages(app, resolverFn) => (req, res)`

The `routeMessages` lets you handle the different types of Data Models and Event Types in different URLs of your express app. For example, if you want to receive all `PatientPush` from the `Clinical Summary` you can use `routeMessages` and later register the following URL `app.post("/ClinicalSummary/PatientPush")`.

`routeMessages` receives the express `app` and optionally a `resolverFn(dataModel, eventType)`. The `resolverFn` is in charge of normalizing the data model and event type names, the default implementation removes spaces and redirects to `/DataModelName/EventTypeName`.

```js
const express = require("express");
const bodyParser = require("body-parser");
const { routeMessages } = require("@ingenious-redox/destination-middleware");
const app = express();

app.use(bodyParser.json());
app.post("/", routeMessages(app));
app.post("/ClinicalSummary/PatientPush", (req, res) => {
  // Do something with req.body
  console.log(req.body);
  res.sendStatus(201);
});

app.listen(process.env.PORT, () =>
  console.log(`Example app listening on port ${process.env.PORT}!`)
);
```
npm package: @ingeno/pipedream-helpers
Description: Helper utilities for Clarity Pipedream integrations
Author: Ingeno
Latest version: 1.0.54

# Clarity Pipedream Helpers

Helper utilities for Clarity Pipedream data integration workflows.

## Installation

```bash
npm install clarity-pipedream-helpers
```

## Usage

```javascript
import { echo } from 'clarity-pipedream-helpers';

export default {
  async run({ steps, $ }) {
    const message = echo("Hello from Pipedream!");
    console.log(message);
    return message;
  }
}
```

## Available Functions

### `echo(message: string): string`

A simple echo function that returns the input message.

**Parameters:**
- `message` - The message to echo

**Returns:**
- The same message

**Example:**
```javascript
import { echo } from 'clarity-pipedream-helpers';

const result = echo("Test message");
console.log(result); // "Test message"
```

## Development

This package is designed to work seamlessly with Pipedream workflows. More helper functions will be added over time to support common data integration patterns.

## License

MIT
npm package: @ingenuity-labs/react-native-async-storage-wrapper
Description: An Async Storage utility wrapper for React Native projects thru the initiative of Ingenuity Labs.
Author: Jason Jon E. Carreos
Latest version: 1.0.3

# react-native-async-storage-wrapper [![NPM version](https://badge.fury.io/js/react-native-async-storage-wrapper.svg)](https://npmjs.org/package/react-native-async-storage-wrapper) [![Build Status](https://travis-ci.org/ingenuityph/react-native-async-storage-wrapper.svg?branch=master)](https://travis-ci.org/ingenuityph/react-native-async-storage-wrapper)

> An Async Storage utility wrapper for React Native projects thru the initiative of Ingenuity Labs.

## Installation

```sh
$ npm install --save @ingenuity-labs/react-native-async-storage-wrapper
```

## Usage
`AsyncStorage` is a collection of utility methods designed to simplify storing of an object to React Native's `AsyncStorage` module. It is composed of three(3) methods.

* `getObjectWithIdentifier(identifier)`
> Retrieves the corresponding object of the provided `identifier` from the storage. It returns a `Promise` object wherein the object is returned when resolve, else, you need to catch the error when it failed to fetch the object.

* `removeObjectWithIdentifier(identifier)`
> Removes the corresponding object of the provided `identifier` to the storage, else, you need to catch the error when it failed to remove the object.

* `setObjectWithIdentifier(object, identifier)`
> Stores the corresponding `object` with its given `identifier` to the storage, else, you need to catch the error when it failed to store the object.

## Contributing

1. Fork repository
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -am 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request

## License

MIT