open-index/open-npm huggingface dataset:
npm package: @lastcall/elasticsearch-migrate
Description: Migration framework for NodeJS/Elasticsearch.
Author: Rob Bayliss
Latest version: 0.0.4

Elasticsearch Migrate
=====================

This is a schema migration framework for Elasticsearch (7+).

To use it:
1. `npm install @lastcall/elasticsearch-migrate`
2. Configure it. 

Configuration:
--------------
To configure migrations, create a new entry in your project's `package.json` with the key `elasticsearch-migrate`.  Example:

```json
{
...
  "elasticsearch-migrate": {
    "root": ".",
    "migrations": ["./dist/migrations/*.js"],
    "elasticsearch": "http://localhost:9200",
    "index": "migrations"
  }
}
```
Each configuration option is optional, with a good default provided. Options are described below:

* **`root`**: The root directory to use when resolving the migrations pattern (defaults to the current working directory).
* **`migrations`**: Glob patterns pointing to migration files, which must be in `.js` format. Defaults to `./migrations/*.js`.
* **`elasticsearch`**: Configuration options for the Elasticsearch client.  May be a string URI, a relative path pointing to a javascript file that exports a fully configured `@elastic/elasticsearch` Client object, or an object specifying the Elasticsearch configuration.
* **`index`**: The Elasticsearch index to use for tracking migration status. Defaults to `migrations`.
npm package: @lastcall/kibana-code-deployer
Description: CLI tool assisting code-based deployments to Kibana
Author: Rob Bayliss
Latest version: 0.0.11

# Kibana-Code-Deployer

This package is a command-line tool that can be used to import and export saved Kibana objects to JSON files in a local directory.  These JSON files can be committed to version control.

Usage
-----

You can install this project using a simple command:
```bash
npm i @lastcall/kibana-code-deployer
```

Once you have it installed, create a configuration file in your project root (`kcd.json`).  The config file will contain information about your Kibana installation, as well as a local directory that will be used to store exported objects.
```json
# kcd.json
{
  "kibana": {
    "url": "THE_URL_TO_KIBANA"
  },
  "directory": "LOCAL_DIRECTORY_TO_PUT_EXPORTS_IN",
}
```

Now you're ready to rock!  To see what would be exported by KCD, run the following command:
```bash
node_modules/.bin/kcd compare
```

To export those objects from you Kibana instance to your local directory, run:
```bash
node_modules/.bin/kcd export-all
```

To import those same objects from your local directory to your Kibana instance, run:
```bash
node_modules/.bin/kcd import-all
```
npm package: @lastcall/metricsync
Description: Metrics Sync ============
Latest version: 0.3.1

Metrics Sync
============

This tool is designed to consume aggregate metrics from several different cloud providers into a single Elasticsearch instance for graphing and measurement.

Configuration
-------------

This tool is configured through a `sync.yml` file that lives in the working directory.  See [sync.yml.example](./sync.example.yml) for more information.

Running
-------

To invoke a sync, run `bin/metricsync`.  The tool will go out and fetch the latest metrics, and push them into Elasticsearch.  It doesn't particularly matter how often you run the sync - all sources generate an ID that will prevent the records from being duplicated in Elasticsearch.

Alternatively, you can run this application with Docker:
```bash
docker run -v ./sync.yml:/app/sync.yml lastcallmedia/metrics-sync 
```

Sources
--------

#### CircleCI

The CircleCI source consumes job information from the CircleCI APIs.  Specifically, it requests the last N builds and pushes them into an Elasticsearch index.

#### Acquia

The Acquia source consumes some of the Stack Metrics data that Acquia's APIs provide. It aggregates them into hourly chunks, and pushes them into an Elasticsearch index.

#### New Relic

The New Relic source consumes hourly aggregates for the HTTPDispatcher metrics on New Relic.

Credits
-------

This project is an independent effort of Last Call Media, but it was born out of a high-level monitoring need discovered while working on the Mass.gov project.
npm package: @lastcallmedia/elasticsearch-migrate
Description: Migration framework for NodeJS/Elasticsearch.
Author: Rob Bayliss
Latest version: 0.0.13

Elasticsearch Migrate
=====================

This is a schema migration framework for Elasticsearch (7+).

To use it:
1. `npm install @lastcall/elasticsearch-migrate`
2. Configure it. 

Configuration:
--------------
To configure migrations, create a new entry in your project's `package.json` with the key `elasticsearch-migrate`.  Example:

```json
{
...
  "elasticsearch-migrate": {
    "root": ".",
    "migrations": ["./dist/migrations/*.js"],
    "elasticsearch": "http://localhost:9200",
    "index": "migrations"
  }
}
```
Each configuration option is optional, with a good default provided. Options are described below:

* **`root`**: The root directory to use when resolving the migrations pattern (defaults to the current working directory).
* **`migrations`**: Glob patterns pointing to migration files, which must be in `.js` format. Defaults to `./migrations/*.js`.
* **`elasticsearch`**: Configuration options for the Elasticsearch client.  May be a string URI, a relative path pointing to a javascript file that exports a fully configured `@elastic/elasticsearch` Client object, or an object specifying the Elasticsearch configuration.
* **`index`**: The Elasticsearch index to use for tracking migration status. Defaults to `migrations`.
npm package: @lastelaphine/eslint-config-base
Description: LastElaphine's ESLint base config
Author: Shailen Patel
Latest version: 1.0.1

## Install

```sh
npm i @lastelaphine/eslint-config-base
```


## Use

```js
module.exports = {
  'root': true,
  
  'extends': [
    '@lastelaphine/eslint-config-base'
  ]
};
```
npm package: @lastelaphine/eslint-config-react
Description: LastElaphine's ESLint config for React components
Author: Shailen Patel
Latest version: 1.0.1

## Install

```sh
npm i @lastelaphine/eslint-config-react
```


## Use

This config is meant to be applied on top of one of the other base configs.

```js
module.exports = {
  'root': true,
  'extends': [
    '@lastelaphine/eslint-config-ts',
    '@lastelaphine/eslint-config-react'
  ]
};
```
npm package: @lastelaphine/eslint-config-ts
Description: LastElaphine's ESLint config for TS libs
Author: Shailen Patel
Latest version: 1.0.6

## Install

```sh
npm i @lastelaphine/eslint-config-ts
```


## Use

```js
module.exports = {
  'root': true,
  'extends': [
    '@lastelaphine/eslint-config-ts',
  ]
};
```
npm package: @lastelaphine/eslint-config-tsx
Description: LastElaphine's ESLint config for TSX apps
Author: Shailen Patel
Latest version: 1.0.6

## Install

```sh
npm i @lastelaphine/eslint-config-tsx
```


## Use

```js
module.exports = {
  'root': true,
  'extends': [
    '@lastelaphine/eslint-config-tsx',
  ]
};
```
npm package: @lastingnote/cli
Description: CLI for LastingNote dead man's switch check-ins
Latest version: 1.1.0

# @lastingnote/cli

CLI for [LastingNote](https://lastingnote.me) dead man's switch check-ins. Designed for AI assistants (Claude Code, etc.) and automation scripts.

## Installation

```bash
npm install -g @lastingnote/cli
```

## Setup

1. Create an API key in the LastingNote web app (Settings > API Keys)
2. Configure the CLI with one of:

```bash
# Option A: Environment variable (recommended)
export LASTINGNOTE_API_KEY=lnk_your_key_here

# Option B: Config file
echo "api_key=lnk_your_key_here" > ~/.lastingnote
```

## Usage

### Check status

```bash
lastingnote status
# Last check-in: 3 days ago. Next due in 27 days. Status: OK
```

### Perform a check-in

```bash
lastingnote checkin
# Checked in successfully.
```

### View history

```bash
lastingnote history
# Date                        Type
# --------------------------------------------------
# 2026-03-13 10:00:00          API Key - Claude
# 2026-03-10 10:00:00          Mobile
```

### JSON output

All commands support `--json` for machine-readable output:

```bash
lastingnote status --json
```

```json
{
  "status": "ok",
  "lastCheckIn": "2026-03-13T10:00:00Z",
  "nextDue": "2026-04-12T10:00:00Z",
  "deadline": "2026-04-19T10:00:00Z",
  "daysUntilDue": 27,
  "daysUntilDeadline": 34
}
```

## Exit Codes

| Code | Meaning |
|------|---------|
| `0` | Success / status OK |
| `1` | Error (network, auth, invalid config) |
| `2` | Action needed (overdue, grace period, frozen) |

Exit codes enable scripting:

```bash
# Exit code 2 = action needed; exit code 1 = error (don't retry blindly)
lastingnote status; [ $? -eq 2 ] && lastingnote checkin
```

## AI Assistant Integration

### Claude Code

Add to your project's `CLAUDE.md`:

```
After completing work, run `lastingnote status` and check me in if needed.
```

Or use it directly:

```
> run `lastingnote status` and check me in if needed
```

### MCP / Tool Use

Use `--json` for structured output:

```bash
lastingnote status --json
lastingnote checkin --json
```

## Configuration

Precedence (highest to lowest):

1. `--api-key <key>` flag
2. `LASTINGNOTE_API_KEY` environment variable
3. `~/.lastingnote` config file (`api_key=lnk_...`)

### Environment Variables

| Variable | Description |
|----------|-------------|
| `LASTINGNOTE_API_KEY` | API key (`lnk_...`) |
| `LASTINGNOTE_URL` | Override API base URL (for development) |

## Development

```bash
cd tools/lastingnote-cli
npm install
npm run build
npm test
```
npm package: @lastline/eslint-config-lastline-react
Description: Lastline's ESLint config extending eslint-config-react-app
Author: Lastline, Inc.
Latest version: 0.2.3

# eslint-config-lastline-react

Lastline's ESLint config extending eslint-config-react-app.

Inspired by [`eslint-config-airbnb-typescript-prettier`](https://github.com/toshi-toma/eslint-config-airbnb-typescript-prettier) but extends [`eslint-config-react-app`](https://www.npmjs.com/package/eslint-config-react-app).

Mostly uses "WARN" level to allow a better DX with eslint-loader.
Code is transpiled when warnings are present but not when errors exists.

In CI treat warnings as errors with ESLint option: `--max-warnings 0`.

# How to use

Install `eslint`, `typescript` with `@lastline/eslint-config-lastline-react`.

```bash
$ npm install eslint typescript eslint-config-lastline-react --save-dev
```

and put into your `.eslintrc.js` file:

```js
module.exports = {
  extends: '@lastline/lastline-react',
};
```

## License

Open source [licensed as MIT](https://github.com/Lastline-Inc/eslint-config-lastline-react/blob/master/LICENSE).
npm package: @lastmileai/lastmileai
Description: Node.js library for LastMile AI API
Author: LastMile AI
Latest version: 0.0.2

# LastMile AI Node.js Library

This library provides access to the LastMile AI API from Node.js. The code should reflect the same API endpoints documented here: https://lastmileai.dev/docs/api

# API Token
This library requires a LastMile AI API Token, which can be obtained from https://lastmileai.dev/settings?page=tokens.

**Important note: this library should only be used from a server-side context, where the API key can be securely accessed. Using this library from client-side browser code will expose your private API key!**

# Installation

```shell
npm install lastmileai
```

# Usage

## Initialize Library with API Key
This library needs to be configured with your API Token (aka API key) obtained above. You can store the API key in an environment variable or alternative secure storage that can be accessed in your server-side code. For example, to initialize the library with the API key loaded from environment variable:

```javascript
import { LastMile } from "lastmileai";

const lastmile = new LastMile({apiKey: process.env.LASTMILEAI_API_KEY ?? ""});
```

## Completions -- Open AI Models
OpenAI completions are supported out-of the box for ChatGPT and GPT3 models:

```javascript
const completion = await lastmile.createOpenAICompletion({
  completionParams: {
    model: "text-davinci-003",
    prompt: "Your prompt here",
  },
});
const responseText = completion.choices[0]?.text;
```

```javascript
const completion = await lastmile.createOpenAIChatCompletion({
  completionParams: {
    model: "gpt-3.5-turbo",
    messages: [
      { role: "user", content: "Your prompt here" },
    ],
  },
});
const responseText = completion.choices[0].message?.content;
```


## Completions -- Custom Models
If you've tuned any GPT3-based custom models in [LastMile](https://lastmileai.dev/models) or by using this library, you can easily perform inference/completions against the context of their associated datasets (stored in the model's embeddings):

```javascript
const model = await lastmile.readModel("Your model ID");

const completion = await lastmile.createOpenAICompletion({
  completionParams: {
    model: "text-davinci-003",
    prompt: "Your prompt here",
  },
  embeddingCollectionId: model.embeddingCollections[0]?.id,
});
const responseText = completion.choices[0]?.text;