open-index/open-npm huggingface dataset:
npm package: @onairosofficial/capacitor-llm-onairos
Description: Reusable Capacitor iOS plugin for the Onairos native ChatGPT connector.
Author: Onairos
Latest version: 0.1.4

# capacitor-llm-onairos

Reusable Capacitor iOS plugin for the native Onairos ChatGPT connector.

## What It Provides

- `OnairosChatGPTNative.connectChatGPTNative({ jwtToken })`
- `OnairosChatGPTNative.closeChatGPTConnector()`
- `OnairosChatGPTNative.openChatGPTConnector()`
- `onairosNativeConnectorEvent` listener updates for ChatGPT status

## Install

```bash
npm install @onairosofficial/capacitor-llm-onairos
npx cap sync
```

## Usage

```js
import { OnairosChatGPTNative } from '@onairosofficial/capacitor-llm-onairos';

await OnairosChatGPTNative.connectChatGPTNative({ jwtToken });
```

The plugin registers under `window.Capacitor.Plugins.OnairosChatGPTNative`, which matches the current SDK lookup path.

Note: the CocoaPods target name is `OnairosofficialCapacitorLlmOnairos`, which is generated from the full scoped package name by Capacitor. The runtime JS plugin name remains `OnairosChatGPTNative`.

## Current Scope

- iOS implementation only
- ChatGPT login, session verification, conversation scrape, memory fetch, and upload through the Onairos import bridge
- extracted from the current `mobile-preview` app host so it can be published and reused

## Release Hardening

- `prepack` obfuscates the JS bridge entrypoint with `javascript-obfuscator`
- `prepack` also strips comments and extra whitespace from the native iOS source files and podspec
- `postpack` restores the original working files after `npm pack` or `npm publish`

## Publish

```bash
npm install
npm run pack:dry-run
npm publish --access public
```
npm package: @onamfc/npm-vuln-scanner
Description: Scan npm packages for vulnerabilities before installation
Author: onamfc
Latest version: 1.0.2

# NPM Vulnerability Scanner

A defensive security tool that scans npm packages for vulnerabilities before installation, helping protect your system from compromised packages.

## Why Use This Tool?

This scanner allows you to check for known vulnerabilities in npm packages BEFORE running `npm install`, protecting your system from potentially malicious or compromised packages.

## Features

- Scans single package.json files
- Supports npm workspaces (monorepos with multiple package.json files)
- Color-coded vulnerability severity levels
- Detailed vulnerability reports with recommendations
- Returns non-zero exit code when vulnerabilities are found (CI/CD friendly)

## Installation

```bash
npm install -g @onamfc/npm-vuln-scanner
```

Or use with npx without installing:

```bash
npx @onamfc/npm-vuln-scanner
```

## Usage

### Command Line

Scan the current directory:

```bash
npm-vuln-scan
```

Scan a specific directory:

```bash
npm-vuln-scan /path/to/project
```

### Programmatic Usage

```javascript
const { scanPackages } = require('@onamfc/npm-vuln-scanner');

async function checkProject() {
  const { success, results } = await scanPackages('/path/to/project');

  if (!success) {
    console.log('Vulnerabilities found!');
    console.log(results);
  }
}

checkProject();
```

## How It Works

1. Discovers all package.json files in the target directory
2. For workspace projects, finds all workspace package.json files
3. Queries the npm registry audit API for each package
4. Reports vulnerabilities by severity (Critical, High, Moderate, Low)
5. Provides detailed information and remediation recommendations

## Vulnerability Severity Levels

- **Critical**: Immediate action required
- **High**: Address as soon as possible
- **Moderate**: Review and plan to address
- **Low**: Review at your convenience

## Exit Codes

- `0`: No vulnerabilities found or scan completed successfully
- `1`: Vulnerabilities found or scan error

## Use in CI/CD

Add to your CI pipeline to prevent deployment of vulnerable dependencies:

```yaml
- name: Scan for vulnerabilities
  run: npx @onamfc/npm-vuln-scanner
```

## Contributing

This is an open source project. Contributions are welcome!

## License

MIT
npm package: @onamfc/pkg-inspect
Description: CLI + API that scans a project and shows dependency size breakdowns
Author: onamfc
Latest version: 1.0.2

# Package Analyzer

CLI + API that scans a project and shows dependency size breakdowns locally.

## Features

- Analyzes installed dependency sizes in `node_modules`
- Shows sorted list of dependencies by size
- Works as both a CLI tool and importable API
- Formatted table output or JSON
- Fast local analysis without external API calls

## Installation

```bash
npm install -g @onamfc/pkg-inspect
```

Or use directly with npx:

```bash
npx @onamfc/pkg-inspect
```

## CLI Usage

Analyze the current directory:

```bash
pkg-inspect
```

Analyze a specific project:

```bash
pkg-inspect /path/to/project
```

Output as JSON:

```bash
pkg-inspect --json
```

Disable colored output:

```bash
pkg-inspect --no-color
```

## API Usage

```javascript
import { analyzeProject, formatSize, formatResults } from '@onamfc/pkg-inspect';

// Analyze a project
const results = await analyzeProject('./my-project');

console.log(`Total size: ${formatSize(results.total)}`);
console.log(`Dependencies found: ${results.dependencies.length}`);

// Format and display results
console.log(formatResults(results));

// Access individual dependency data
results.dependencies.forEach(dep => {
  console.log(`${dep.name}: ${formatSize(dep.size)}`);
});
```

## API Reference

### `analyzeProject(projectPath)`

Analyzes dependencies in a project.

**Parameters:**
- `projectPath` (string, optional) - Path to project directory. Defaults to current working directory.

**Returns:** Promise that resolves to:
```javascript
{
  total: 258254,                    // Total size in bytes
  dependencies: [
    {
      name: "package-name",
      version: "^1.0.0",
      size: 123456                  // Size in bytes
    }
  ],
  projectPath: "/path/to/project"
}
```

### `formatSize(bytes)`

Formats byte size to human-readable string.

**Parameters:**
- `bytes` (number) - Size in bytes

**Returns:** String (e.g., "1.23 MB", "456.78 KB")

### `formatResults(results)`

Formats analysis results as a readable table.

**Parameters:**
- `results` (object) - Results from `analyzeProject()`

**Returns:** Formatted string ready to display

## Example Output

```
📦 Package Size Analysis

────────────────────────────────────────────────────────────
Total Size: 252.20 KB

Package                                             Size
────────────────────────────────────────────────────────────
commander                                      182.03 KB
picocolors                                      15.20 KB
ora                                             26.87 KB
────────────────────────────────────────────────────────────

💡 Top 3 largest dependencies:
   1. commander
   2. ora
   3. picocolors
```

## How It Works

Unlike other packages that fetch data from npm, `pkg-inspect` analyzes your actual installed `node_modules` directory. This gives you:

- Real sizes after installation (not theoretical npm package sizes)
- Analysis of your specific version and dependencies
- No network requests needed
- Fast local analysis

## License
MIT