open-index/open-npm huggingface dataset:
npm package: @mmmbuto/masix
Description: Termux-first MIT automation runtime for Android/Termux; Linux/macOS supported via source builds and Homebrew; bundled plugin-base packages auto-install or auto-build as needed
Author: Davide A. Guglielmi
Latest version: 0.4.18

# @mmmbuto/masix

Official npm package for the Termux distribution of MasiX (MIT).

MasiX is Termux-first. Linux and macOS are supported through source builds and the Homebrew tap.

Current package line: `0.4.14`.

## Function Summary

- Telegram bot automation with interactive inline menus
- Real MCP tool-calling flow through API-compatible endpoints
- Natural-language reminder scheduling with cron persistence
- Cron scope isolation per bot/account (`account_tag`)
- Workdir isolation per Telegram account
- User memory isolation with per-user catalog (`meta.json`)
- Termux wake lock control (`masix termux wake on|off|status`)
- Guarded command execution (`/exec`, `/termux`) with allowlists
- Termux boot automation (`masix termux boot enable|disable|status`)
- Optional local STT via whisper.cpp (`masix config stt`)
- Bundled `plugin-base` packages are included and installed during `npm install`
- If a bundled `.pkg` is missing, MasiX can fall back to source build for the module
- Startup update checks are available on demand via `masix check-update`

## Install (Termux)

```bash
pkg update -y
pkg install -y rust nodejs-lts termux-api
npm install -g @mmmbuto/masix@latest
masix --help
```

## Quick Start

```bash
masix setup init
masix setup doctor
masix start
masix status
```

## Bundled Packages

Postinstall installs this default bundled `plugin-base` package into `~/.masix/plugins`:
- `discovery` `0.3.0`

Legacy manual-only bundled plugins still shipped in the tarball:
- `codex-backend` `0.1.4`
- `codex-tools` `0.1.3`

Package artifacts and source trees are included in the npm tarball under `packages/plugin-base/`.

## Useful Commands

```bash
masix start
masix config show
masix config validate
masix config stt
masix cron add 'domani alle 9 "Daily check"'
masix cron list
masix cron cancel 1
masix cron list --account-tag 123456789
masix termux boot status
masix stats
```

## Notes

- This package targets Android + arm64 in Termux
- If the packaged prebuilt is missing or has a version mismatch, postinstall rebuilds from the bundled `workspace/` mirror
- The postinstall step uses `masix plugin install-base` and now keeps only the recommended base path
- `masix config stt` can auto-pick and auto-download a Whisper model based on device resources

## Full Documentation

- Repository README: https://github.com/DioNanos/MasiX
- Detailed guide: https://github.com/DioNanos/MasiX/blob/main/docs/USER_GUIDE.md
- Commands reference: https://github.com/DioNanos/MasiX/blob/main/docs/COMMANDS_REFERENCE.md
- Homebrew tap: https://github.com/DioNanos/homebrew-masix
- Local llama.cpp endpoint guide: https://github.com/DioNanos/MasiX/blob/main/docs/TERMUX_LLAMA_CPP_LOCAL_ENDPOINT.md

## Branding

<p>
Copyright (c) 2026 Davide A. Guglielmi<br>
Made in Italy 🇮🇹
</p>

## License

MIT - See `../../LICENSE`
npm package: @mmmbuto/node-pty-android-arm64
Description: Android/Termux-only fork of node-pty for ARM64 (bionic)
Author: Microsoft Corporation
Latest version: 1.1.0

# node-pty-android-arm64

Android/Termux-only fork of node-pty targeting ARM64 (bionic). It provides the same API as the upstream `node-pty` package but is focused on working reliably under Termux.

## Scope

- Platform: `android`
- CPU: `arm64`
- Intended environment: Termux on Android

If you need Linux/macOS/Windows support, use the upstream project: https://github.com/microsoft/node-pty

## Install

```bash
npm install node-pty-android-arm64
```

If you want to keep `require('node-pty')` in your code, you can use an npm alias:

```bash
npm install node-pty@npm:node-pty-android-arm64
```

## Build on Termux

Prerequisites:

```bash
pkg install -y nodejs python make clang pkg-config git
```

Build and install:

```bash
npm install
npm run build
```

Notes:
- If `prebuilds/android-arm64` exists, it will be used.
- When building from source on Termux, `android_ndk_path` is derived from `ANDROID_NDK_HOME`/`ANDROID_NDK_ROOT` or falls back to `$PREFIX`.

## Usage

```js
import * as os from 'node:os';
import * as pty from 'node-pty';

const shell = os.platform() === 'win32' ? 'powershell.exe' : 'bash';

const ptyProcess = pty.spawn(shell, [], {
  name: 'xterm-color',
  cols: 80,
  rows: 30,
  cwd: process.env.HOME,
  env: process.env
});

ptyProcess.onData((data) => {
  process.stdout.write(data);
});

ptyProcess.write('ls\r');
```

## Credits

Based on the original `node-pty` project by Microsoft and contributors.
npm package: @mmmbuto/zork-termux
Description: ZORK I, II, III for Termux terminal with prebuilt binary
Author: Davide A. Guglielmi
Latest version: 0.4.2

# @mmmbuto/zork-termux

NPM distribution for **zork-termux** focused on **Android Termux (arm64)**.

## Prerequisites

```bash
pkg update
pkg install -y nodejs-lts
```

## Install

```bash
npm i -g @mmmbuto/zork-termux
```

## Run

```bash
zork-termux
```

## Notes

- This package expects a prebuilt `prebuilt/zork-termux` binary.
- If prebuilt is missing, install fails and asks to reinstall from npm release.
- Linux/macOS users should use Homebrew tap:

```bash
brew tap Dionanos/zork-termux
brew install zork-termux
```
npm package: @mmmcorp/angular-mock-generator
Description: `Anuglar.js 1.x`を用いたアプリケーションのテストのためにAPIレスポンスのモックを生成するライブラリ
Latest version: 0.1.11

`Anuglar.js 1.x`を用いたアプリケーションのテストのためにAPIレスポンスのモックを生成するライブラリ

## 目的

APIレスポンスを模したオブジェクトから、`Angular.js`/`Node.js`のモジュールシステムでそれぞれ使用できるモックを生成する  
`Angular.js`の`Value Service`として生成され、ベースとなったファイルへのパスから`Service`としての名前を`camelCase`で決定する

```js
// /path/to/base/file/my-file.js
// こういうオブジェクトから...
module.exports = {
  foo: 'bar'
};

// Angular.jsのモジュールとして直接ブラウザに読み込ませるためのモック
// /path/to/base/file/my-file.angular.js として生成される
angular.module('httpBackendMock').value('pathToBaseFile', {
  "foo": "bar"
});

// ProtractorのaddMockModuleメソッドに追加するためのモック
// /path/to/base/file/my-file.node.js として生成される
module.exports = function() {
  angular.module('httpBackendMock').value('pathToBaseFile', {
    "foo": "bar"
  });
};
```

## 使い方

CLIツールとして使用する。  
第一引数に設定ファイルを渡すことで、モックモジュールの生成元となるファイルを指定する

設定ファイルには以下の3つのパラメータがある  
※このレポジトリでは`mock.conf.js`というファイル名になっているが、ファイル名の指定は無い

```js
module.exports = {
  // Aungular.jsのモジュールシステムにおけるモジュールの名前を指定する
  moduleName: 'httpBackendMock',

  // globパターンでモックモジュールの生成元となるファイル郡を指定する
  files: [
    'sample/*.js',
    'sample/**/*.js',
  ],

  // デバッグモードをオンにすると、どんなファイルが生成されるか標準出力で確認できる
  isDebug: false,
};
```
npm package: @mmmcorp/react-file-input
Description: Simple file input component for React
Author: Captivation Software
Latest version: 0.2.6

react-file-input
============
[Demo](https://captivationsoftware.github.io/react-file-input)

Styling native HTML file inputs can be a pretty big pain, and to make matters worse, the browser default look-and-feel is probably at odds with your app's design. This problem is what react-file-input aims to solve.

Once integrated, react-file-input quickly eliminates the headaches associated with forms requiring file upload.

## Installation
```sh
npm install react-file-input
```

## Code Example
Usage is pretty simple: just use react-file-input instead of `<input type="file" />`!

app.jsx
```js
var React = require('react'),
  FileInput = require('react-file-input');

var Form = React.createClass({
  handleChange: function(event) {
    console.log('Selected file:', event.target.files[0]);
  },

  render: function() {
    return (
      <form>
        <FileInput name="myImage"
                   accept=".png,.gif"
                   placeholder="My Image"
                   className="inputClass"
                   onChange={this.handleChange} />
      </form>
    );
  },
});

```

The list of valid props can be found below.

### Props

#### name, accept, className, placeholder, onChange
Behave just like standard react-style attributes on input controls.

## Contributors

Captivation Software (@teamcaptivation)

By all means, if you see room for improvement, let us know!


## License

MIT License
npm package: @mmmeff/use-s3-uploader
Description: use-s3-uploader ===========================
Author: Matthew Frey
Latest version: 1.6.0

use-s3-uploader
===========================

From Browser
------------

```jsx
  import React, { useRef } from 'react';
  import { useS3Uploader } from '@mmmeff/use-s3-uploader';

  const Example = (props) => {
    const inputRef = useRef(null);

    const getSignedUrl = (file, next) => {
      next({
        signedUrl: "https://example.amazonaws.com/test.jpg?x-amz-acl=......."
      });
    };

    const onUploadStart = (file, next) => {
      next(file);
    }

    const onProgress = (percent, status, file) => {
      console.log('onProgress', percent, status, file)
    }

    const onError = (error, file) => {
      console.log(error, file)
    }

    const onFinish = (signResult, file) => {
      console.log(signResult, file);
    }

    useS3Uploader({
      getSignedUrl: getSignedUrl,
      onUploadStart: onUploadStart,
      onProgress: onProgress,
      onError: onError,
      onFinish: onFinish,
      accept: 'image/*',
      uploadRequestHeaders: (file) => ({
      }),
      contentDisposition: 'auto',
    }, inputRef);

    return (
      <div>
        <input type='file' ref={inputRef} multiple={true} />
      </div>
    )
  }

  export default Example;
```
npm package: @mmmoli/effect-otel-workers
Description: Effect-TS + OpenTelemetry support for Cloudflare Workers
Author: Michele Memoli
Latest version: 0.1.3

Effect TS Tracing on Cloudflare Workers
=======================================

# Setup

Enable 'nodejs_compat' inside your worker:

```
"compatibility_flags": ["nodejs_compat"],
```

Let's start with the Gotchas.

## Gotchas

### CF Worker !== node

For me, this stopped any of the basic implementations working from Effect TS docs:

```
const NodeSdkLive = NodeSdk.layer(() => ({
  resource: { serviceName: "example" },
  // Export span data to the console
  spanProcessor: new BatchSpanProcessor(new ConsoleSpanExporter())
}))
```

Won't work because both `BatchSpanProcessor` and `ConsoleSpanExporter` are incompatible with Cloudflare Workers (as far as I can tell).

### `ConsoleSpanExporter`

Didn't print anything inside my react-router app.

### `BatchSpanProcessor`

Essential for production, this Span Processor will colled spans together before sending them to your OpenTelemetry backend.

I couldn't get it to work with Cloudflare Workers out of the box.

## Some light at the end of the tunnel

The [evanderkoogh/otel-cf-workers repo](https://github.com/evanderkoogh/otel-cf-workers) gets Workers working out of the box. So the only challenge is making these components work with Effect.
npm package: @mmmz/ali-sls
Description: Warning: This is a work-in-progress and not the finished product.
Author: xuerzong
Latest version: 0.0.1-beta.0

# ali-sls

Warning: This is a work-in-progress and not the finished product.

## How to use

```bash
yarn add @ninepielabs/ali-sls
```

```typescript
import { initClient, client } from '@ninepielabs/ali-sls'

initClient({
  endpoint: <your-endpoint>
  project: <your-project>
  accessKeyId: process.env.ALI_ACCESS_KEY_ID
  accessKeySecret: process.enve.ALI_ACCESS_KEY_SECRET
})

client.get('/path/to/', {
  params: {},
  data: {}
})
```
npm package: @mmn-systems/n8n-nodes-mcp-trigger-context
Description: Community MCP Trigger node with request context passthrough
Latest version: 0.2.3

# n8n-nodes-mcp-trigger-context

Community MCP Trigger node for current n8n 2.x installations that forwards incoming MCP HTTP request context into tool execution input as `mcpRequest`.

## Install

```bash
npm install @mmn-systems/n8n-nodes-mcp-trigger-context
```

Repository: https://github.com/max00346/n8n-nodes-mcp-trigger-context

## What it solves

Built-in MCP trigger tool calls do not expose HTTP headers/query/path directly to tool parameter expressions.

This node injects:

- `$json.mcpRequest.headers`
- `$json.mcpRequest.query`
- `$json.mcpRequest.params`
- `$json.mcpRequest.method`
- `$json.mcpRequest.path`

For MCP tool calls on current n8n 2.x, the same request context is also embedded into the internal `mcpToolCall.arguments` payload so queue-mode worker executions receive the same header/query/path context as direct executions.

## Example

In a connected HTTP Request tool/node expression:

```text
={{ $json.mcpRequest.headers.authorization }}
```

## Notes

- Targets current n8n 2.x MCP Trigger internals.
- Requires n8n installations that include `@n8n/n8n-nodes-langchain`.

## Troubleshooting

If n8n shows `Class could not be found` after upgrading:

1. Remove the old package from Community Nodes in n8n.
2. Stop n8n and delete the old install at `~/.n8n/nodes/node_modules/@mmn-systems/n8n-nodes-mcp-trigger-context`.
3. Start n8n and install a pinned version, for example `@mmn-systems/n8n-nodes-mcp-trigger-context@0.1.6`.