open-index/open-npm huggingface dataset:
npm package: @funeste38/allmight
Description: Audit-first duplicate detector and canonicalization helper for Funesterie repositories.
Author: jEFFLEZ
Latest version: 1.2.0

# @funeste38/allmight

`allmight` audits repositories for duplicate code families, picks a canonical source, and proposes safe transition patches instead of destructive cleanup.

## Goals

- detect exact and near duplicates
- identify nested package mirrors and competing barrels
- propose a canonical source per family
- generate traceable reports and diff proposals
- apply only safe patches on explicit request

## CLI

```bash
allmight scan <root>
allmight report <root>
allmight propose <root>
allmight fix-safe <root>
allmight canonicalize <root>
allmight scan <root> --ignore-dir docs --ignore-ext .md --ignore-path tmp/
```

Outputs:

- `duplicate-report.json`
- `canonical-map.json`
- `patches/*.diff`
- `summary.md`

Useful filters:

- `--ignore-dir <name>` skips matching directory names in addition to the default ignores
- `--ignore-ext <ext>` skips a file extension such as `.md`
- `--ignore-path <token>` skips any relative path containing that token, useful for `tmp/`, `docs/`, or `generated/`

## Design

- audit-first by default
- never deletes divergent logic automatically
- preserves runtime transitions with shims when possible
- favors traceability over hidden cleanup
npm package: @funeste38/bat
Description: Adaptive request-control primitives for resilient network, tool and AI orchestration.
Author: funeste38
Latest version: 1.0.3

# @funeste38/bat

`bat` is the published adaptive request-control package from the Funesterie ecosystem.

It gives you a small vocabulary of runtime components to observe latency, classify response quality, adapt request behaviour and rotate channels when a single path becomes unreliable.

## Install

```bash
npm install @funeste38/bat
```

## Core primitives

- `Bat`: raw sensing and RTT capture
- `Ears`: qualitative analysis of answers or channel noise
- `Wings`: adaptation logic, pacing and cooldown
- `Fangs`: multi-channel execution
- `Inversion`: escape hatch when BAT should be bypassed

## Quick example

```ts
import { Bat, Ears, Wings, Fangs } from "@funeste38/bat";

const bat = new Bat();
const ears = new Ears();
const wings = new Wings();
const fangs = new Fangs({ channels: [] });
```

## Use cases

- resilient proxy rotation
- multi-provider AI calling
- local tool execution with adaptive retry logic
- experimental orchestration around unstable channels

## Development

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

## Local references

- `src/demo.ts`
- `test/basic.test.js`

## Good next improvements

- document concrete HTTP channel examples
- add typed events for telemetry and scoring
- expose a higher-level orchestrator preset for QFLUSH
npm package: @funeste38/beam
Description: Pipeline orchestration primitives for Funesterie and QFLUSH.
Author: funeste38
Latest version: 1.0.2

# @funeste38/beam

`beam` is the pipeline vocabulary layer for Funesterie.

It gives QFLUSH and related tools a small, typed way to describe execution styles such as streaming, targeted mutation, batch processing and multi-phase orchestration. The Dragon Ball inspired aliases are optional sugar on top of a real technical model.

## What it does

- Normalizes friendly aliases like `kamehameha`, `gogeta`, or `genkidama`
- Routes jobs to one of five pipeline families: `beam`, `drill`, `bomb`, `fusion`, `ultra`
- Lets host systems inject their own handlers and services
- Ships a ready-to-use QFLUSH adapter via `runQflushBeam()`

## Install

```bash
npm install @funeste38/beam
```

## Quick start

```ts
import { runQflushBeam } from "@funeste38/beam";

const result = await runQflushBeam({
  type: "gogeta",
  source: "repo:/",
  target: "cortex:/encode",
  payload: { file: "D:/img.png" }
});

console.log(result.ok, result.type, result.logs);
```

## Pipeline families

| Type | Purpose | Typical use |
| --- | --- | --- |
| `beam` | Continuous flow | streaming transforms, encoding, transfer |
| `drill` | Precision work | targeted patches, block edits, pixel or offset rewrites |
| `bomb` | Batch / aggregate | repo scans, multi-file passes, reporting |
| `fusion` | Multi-phase combo | combine `beam`, `drill`, and `bomb` |
| `ultra` | Full orchestration | end-to-end pipeline with optimisation pass |

## Alias system

`beam` accepts both technical names and Funesterie aliases.

- `kame`, `kameha`, `kamehameha` -> `beam`
- `mkp`, `makanko`, `makankosappo`, `specialbeam` -> `drill`
- `genki`, `genkidama`, `spiritbomb` -> `bomb`
- `gogeta`, `vegito`, `fusiondance` -> `fusion`
- `ssj`, `god`, `limitbreaker`, `superfunesterie` -> `ultra`

## Main API

### `dispatchBeam(job, ctx)`

Low-level dispatcher that resolves aliases and calls the matching handler.

### `createQflushBeamContext(opts)`

Creates a `BeamContext` with default QFLUSH-oriented handlers.

### `runQflushBeam(job, opts?)`

Convenient high-level entry point for QFLUSH integrations.

## Current limitations

The included handlers are intentionally conservative and some remain placeholders. The package already defines the orchestration contract cleanly, but the most advanced execution logic still belongs in host systems like QFLUSH, CORTEX, or SPYDER.

## Good next improvements

- Add first-class metrics per pipeline phase
- Expose composable middleware before and after each handler
- Replace placeholder optimisation with deterministic planner output
- Add fixtures for real QFLUSH/CORTEX jobs

## Development

```bash
npm install
npm run build
npm test
```
npm package: @funeste38/freeland-bros
Description: Freeland Bros - cube diagnostics, runtime solving and RGBA projection layer on top of freeland and morphing.
Author: funeste38
Latest version: 0.1.0

# @funeste38/freeland-bros

`freeland-bros` is the visual and diagnostic layer on top of `freeland`.

Where `freeland` answers:

- what is this value?
- how is it normalized?
- is it compatible with a target runtime?

`freeland-bros` answers:

- how do I project that value into a stable RGBA / cube space?
- how do I explain incompatibility quickly?
- what is the minimal transition plan from one runtime target to another?

It uses:

- `freeland` for typed resolution
- `@funeste38/morphing` for RGBA / compact transport primitives

## Install

```bash
npm install @funeste38/freeland-bros
```

## Main ideas

Every resolved value becomes a cube:

- `r` = kind
- `g` = format
- `b` = runtime
- `a` = state

Example:

```ts
{
  r: "executable",
  g: "native-binary",
  b: "railway",
  a: "compatible"
}
```

## API

- `resolveBrosCube(input, options)` resolves a Freeland input and returns both the typed value and the cube
- `brosCubeFromValue(value, runtime?)` projects an existing Freeland value into cube space
- `diagnoseBrosCompatibility(valueOrCube, targetRuntime)` returns a short compatibility report
- `buildBrosTransitionPlan(valueOrCube, targetRuntime)` returns symbolic transitions
- `projectBrosCubeToRgba(cube)` returns an RGBA tuple via `morphing`
- `rotateBrosCube(cube, axis, turns?)` applies deterministic symbolic rotations

## Example

```ts
import {
  resolveBrosCube,
  diagnoseBrosCompatibility,
  projectBrosCubeToRgba
} from "@funeste38/freeland-bros";

const { value, cube } = await resolveBrosCube(
  'manifest:json:{"kind":"executable","variants":{"windows":"path:./bin/piper.exe","linux":"path:./bin/piper"}}',
  { runtime: "railway" }
);

const diagnostic = diagnoseBrosCompatibility(value, "railway");
const rgba = projectBrosCubeToRgba(cube);

console.log(value, cube, diagnostic, rgba);
```

## Why this package exists

This layer keeps the core packages clean:

- `freeland` stays a parser / normalizer / adapter
- `morphing` stays a low-level binary primitive
- `freeland-bros` handles symbolic cube logic, visual projection and explanation

## Development

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

## License

MIT
npm package: @funeste38/nezlephant
Description: OC8 PNG encode/decode helpers plus Rubik-style block scrambling utilities.
Latest version: 1.0.4

# @funeste38/nezlephant

`nezlephant` is the OC8 image payload helper from the Funesterie ecosystem.

It lets you hide small binary payloads inside PNG pixels, decode them back, and optionally scramble image blocks with a stable key-based permutation for visual obfuscation.

## Install

```bash
npm install @funeste38/nezlephant
```

## Core API

- `encodeToOC8Png(payload, width?, height?)`
- `decodeFromOC8Png(pngBuf)`
- `scramblePngBlocks(pngBuf, key, blockSize?)`
- `unscramblePngBlocks(pngBuf, key, blockSize?)`
- `crc8(buf)`

## Example

```js
const {
  encodeToOC8Png,
  decodeFromOC8Png,
  scramblePngBlocks,
  unscramblePngBlocks
} = require('@funeste38/nezlephant');

const payload = Buffer.from('secret-data');
const png = encodeToOC8Png(payload, 16, 16);
const scrambled = scramblePngBlocks(png, 'ma-cle-secrete', 4);
const restored = unscramblePngBlocks(scrambled, 'ma-cle-secrete', 4);
const decoded = decodeFromOC8Png(restored);

console.log(decoded.toString('utf8'));
```

## Security Notes

- OC8 is obfuscation, not encryption
- Rubik scrambling is a deterministic permutation, not a cryptographic scheme
- for real confidentiality, encrypt first and encode second

## Development

```bash
npm install
npm test
```
npm package: @funeste38/rome
Description: Tous les chemins mènent à Rome — CLI avancée pour monorepos avec gestion des processus détachés, auto-workspaces et compatibilité cross-platform.
Author: jEFFLEZ
Latest version: 1.5.5

# @funeste38/rome

**Tous les chemins mènent a Rome**.

`rome` is the Funesterie CLI for local monorepos, detached processes and cross-platform developer workflows. It is built to make Windows, PowerShell and mixed workspaces feel first-class instead of second-class.

[![npm version](https://img.shields.io/npm/v/@funeste38/rome.svg)](https://www.npmjs.com/package/@funeste38/rome)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

## What Rome does well

- discovers workspaces automatically in common monorepo layouts
- runs one, two or three services with prefixed logs
- supports detached processes and monitoring helpers
- fixes working-directory problems before they become annoying
- stays scriptable from PowerShell, Node or CI

## Install

```bash
npm install @funeste38/rome
```

## Quick start

```bash
# run a command inside a detected workspace
rome run server -- npm run dev

# launch two workspaces in parallel
rome duo server "npm run dev" web "npm run dev"

# smart launcher: 1 workspace -> run, 2 -> duo, 3 -> trio
rome start
```

## Main commands

### Workspace execution

```bash
rome run api -- npm run dev
rome fix web -- npm run build
rome build
rome test
rome lint
rome clean
```

### Parallel workflows

```bash
rome duo server "npm run dev" web "npm run dev"
rome trio api "npm run dev" web "npm run dev" ai "npm run start"
```

### Detached and monitored processes

Use `rome.json` to define long-lived processes and let Rome manage logs, restarts and lifecycle more cleanly than ad-hoc shell tabs.

### Tunnel helpers

```bash
rome tunnel up 3000
rome tunnel status
rome tunnel test
rome tunnel down
```

## Workspace detection

Rome looks for familiar names and folders such as:

- root folders like `server`, `backend`, `api`, `web`, `client`, `app`
- nested folders like `apps/`, `packages/`, `services/`, `src/`
- recursive descendants when you launch it from a larger workspace

## Environment support

Environment support is optional. Rome can integrate with the newer Funesterie stack:

- `@funeste38/envaptex` for env loading and typed profiles
- `freeland` for value normalization across prefixes like `json:`, `b64:`, `file:` and `nez:`
- `@funeste38/nezlephant` for OC8 PNG-based payload transport when needed

Example:

```bash
rome env check --profile dev
rome env generate web --profile production --out apps/web/.env.production
```

Rome keeps these integrations dynamic, so projects that only need workspace orchestration do not pay extra complexity.

## Good next improvements

- richer JSON logs for desktop supervisors and cloud hosts
- first-class process groups beyond `duo` and `trio`
- native status dashboard for detached processes
- stronger env profile diffing and validation output

## Development

```bash
npm install
npm run build
```
npm package: @funeste38/scream
Description: Semantic prototype for SCREAM, WAZAA and MASK in the Funesterie ecosystem.
Author: jEFFLEZ
Latest version: 0.1.0

# @funeste38/scream

`scream` is a small semantic prototype for the Funesterie stack.

It exposes three layers:

- `SCREAM`: text to resonance graph
- `WAZAA`: text to intermediate semantic structure
- `MASK`: normalize, validate and compile the semantic structure

## Install

```bash
npm install @funeste38/scream
```

## API

```js
const {
  textToResonanceGraph,
  textToWazaa,
  wazaaToMask,
  validateMask,
  compileMask
} = require("@funeste38/scream");
```

### `textToResonanceGraph(text)`

Returns a simple graph-oriented placeholder structure:

```js
{
  input: text,
  resonanceGraph: [],
  meta: {}
}
```

### `textToWazaa(text)`

Returns a semantic intermediate placeholder:

```js
{
  input: text,
  wazaa: {},
  meta: {}
}
```

### `wazaaToMask(wazaa)`

Builds a first MASK-shaped object:

```js
{
  intent: wazaa.intent || "unknown",
  inputs: wazaa.inputs || {},
  meta: wazaa.meta || {}
}
```

### `validateMask(mask)`

Checks the minimal contract:

- `valid: true` when `intent` exists
- an `errors` array otherwise

### `compileMask(mask)`

Returns a placeholder compiled payload:

```js
{
  compiled: mask
}
```

## Development

```bash
npm install
npm test
```
npm package: @funeste38/spyder
Description: Spyder package for Funesterie — local assistant components
Author: jEFFLEZ
Latest version: 1.0.6

# @funeste38/spyder

`spyder` packages the lightweight local assistant primitives of the Funesterie ecosystem.

It focuses on a small programmable server surface rather than a giant framework: start a TCP-aware runtime, keep a simple in-memory state, and bridge packets or events to another service such as A11.

## Install

```bash
npm install @funeste38/spyder
```

## What You Get

- `createSpyderServer(...)` to start a small Spyder runtime in-process
- a simple memory object attached to the running server
- a custom `sendToA11` bridge hook so A11 integration stays explicit
- a package that is small enough to embed into local tooling or automation

## Quick Example

```ts
import { createSpyderServer } from "@funeste38/spyder";

const server = createSpyderServer({
  port: 4500,
  sendToA11: async (payload) => {
    console.log("bridge payload", payload);
    return new Uint8Array();
  }
});

await server.start();
await server.stop();
```

## Development

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

## Notes

- this package is intentionally local-first
- deeper socket and protocol integrations can be layered on top
- if you need the larger orchestration stack, use `@funeste38/qflush`
npm package: @funesterie/katana
Description: CLI to slice large Node backends into route and service extraction plans.
Author: Funesterie
Latest version: 0.1.1

# Katana

`katana` scans oversized Node/Express files and produces an extraction plan for routes, helpers, and service families.

It is built for situations like a 10k+ line `server.cjs` where you need a safe first pass before manual refactors.

## Install

```bash
npm i -g @funesterie/katana
```

Or run it without installing:

```bash
npx @funesterie/katana scan apps/server/server.cjs --stdout md
```

## What it does

- detects route declarations such as `app.get(...)`, `app.post(...)`, `app.use(...)`
- detects helper/function declarations
- groups routes by API family
- groups helpers by domain keywords such as memory, auth, mail, resources, runtime
- suggests module targets and extraction order
- emits text, markdown, and JSON reports

## Usage

```bash
katana scan apps/server/server.cjs
katana scan apps/server/server.cjs --stdout md
katana scan apps/server/server.cjs --json katana-report.json --md katana-report.md
katana scan apps/server/server.cjs --top 12 --root D:/funesterie/a11/a11backendrailway
```

## Example Output

```text
Katana report for apps/server/server.cjs
- 12640 lines
- 42 routes
- 318 helper/function declarations

Top candidate cuts
1. memory -> apps/server/src/services/memory.cjs
2. resources -> apps/server/src/services/resources.cjs
3. auth -> apps/server/src/routes/auth.cjs
```

## Exit Codes

- `0`: report generated
- `1`: invalid usage or file read failure

## Notes

Katana does not rewrite files yet. It creates a reliable cut map first so the real extraction can happen in small, testable slices.
npm package: @funfunz/azure-blob-storage-connector
Description: azure blob storage connector for Funfunz
Author: João Leite
Latest version: 0.5.0

# Funfunz Azure Blob Storage Connector

[![Discord][discord-badge]][discord]
[![Build Status][actions-badge]][actions]
[![codecov][codecov-badge]][codecov]
![node][node]
[![npm version][npm-badge]][npm]
[![PRs Welcome][prs-badge]][prs]
[![GitHub][license-badge]][license]

## Documentation

Just follow the [link](https://funfunz.github.io/funfunz/#/usage/dataConnectors/azure-blob-storage)

## Features

This connector uses @azure/storage-blob npm package to connect to Azure Blob Storage service


[discord-badge]: https://img.shields.io/discord/774439225520554004?logo=discord
[discord]: https://discord.gg/HwZ7zMJKwg

[actions-badge]: https://github.com/funfunz/azure-blob-storage-connector/workflows/Node.js%20CI/badge.svg
[actions]: https://github.com/Funfunz/azure-blob-storage-connector/actions

[codecov-badge]: https://codecov.io/gh/Funfunz/azure-blob-storage-connector/branch/main/graph/badge.svg
[codecov]: https://codecov.io/gh/Funfunz/azure-blob-storage-connector

[node]: https://img.shields.io/node/v/funfunz.svg

[npm-badge]: https://badge.fury.io/js/funfunz.svg
[npm]: https://badge.fury.io/js/funfunz

[prs-badge]: https://img.shields.io/badge/PRs-welcome-brightgreen.svg
[prs]: http://makeapullrequest.com

[license-badge]: https://img.shields.io/github/license/JWebCoder/funfunz.svg
[license]: https://github.com/JWebCoder/funfunz/blob/master/LICENSE
npm package: @funfunz/core
Description: backoffice generator
Author: João Moura
Latest version: 0.25.0

# Funfunz

[![Discord][discord-badge]][discord]
[![Build Status][actions-badge]][actions]
[![codecov][codecov-badge]][codecov]
![node][node]
[![npm version][npm-badge]][npm]
[![PRs Welcome][prs-badge]][prs]
[![GitHub][license-badge]][license]

## Documentation

Just follow the link: https://funfunz.github.io/funfunz/

## What is Funfunz?

Funfunz was created due the lack of a functional back office generator in the NodeJS community.

The goal is to generate a fully automated back office that can be used to directly handle all the database data.

**Features:**
- CRUD operations
- Table search
- MySQL parser
- Friendly name generator for table names and fields

[discord-badge]: https://img.shields.io/discord/774439225520554004?logo=discord
[discord]: https://discord.gg/HwZ7zMJKwg

[actions-badge]: https://github.com/funfunz/funfunz/workflows/Node.js%20CI/badge.svg
[actions]: https://github.com/Funfunz/funfunz/actions

[codecov-badge]: https://codecov.io/gh/Funfunz/funfunz/branch/master/graph/badge.svg
[codecov]: https://codecov.io/gh/Funfunz/funfunz

[node]: https://img.shields.io/node/v/@funfunz/core

[npm-badge]: https://img.shields.io/npm/v/@funfunz/core?color=brightgreen
[npm]: https://www.npmjs.com/package/@funfunz/core

[prs-badge]: https://img.shields.io/badge/PRs-welcome-brightgreen.svg
[prs]: http://makeapullrequest.com

[license-badge]: https://img.shields.io/github/license/funfunz/funfunz.svg
[license]: https://github.com/funfunz/funfunz/blob/master/LICENSE
npm package: @funfunz/dynamodb-data-connector
Description: dynamodb data connector for Funfunz
Author: João Moura
Latest version: 0.1.2

# Funfunz DynamoDB Data Connector

[![Discord][discord-badge]][discord]
[![Build Status][actions-badge]][actions]
[![codecov][codecov-badge]][codecov]
![node][node]
[![npm version][npm-badge]][npm]
[![PRs Welcome][prs-badge]][prs]
[![GitHub][license-badge]][license]

This connector can be used to connect to any DynamoDB table

At the moment, the connector is using the local machine AWS credentials

## Usage

**Dynamo config**

```js
{
  connectors: {
    [key: string]: { // user defined name for the connector
      type: '@funfunz/dynamodb-data-connector',
      config: {
        region: 'eu-west-1'
      }
    }
    ...
  }
}
```

## Entity structure

Refer to [@Funfunz/core](https://funfunz.github.io/funfunz/#/configuration/settings) docs

[discord-badge]: https://img.shields.io/discord/774439225520554004?logo=discord
[discord]: https://discord.gg/HwZ7zMJKwg

[actions-badge]: https://github.com/funfunz/dynamodb-data-connector/workflows/Node.js%20CI/badge.svg
[actions]: https://github.com/Funfunz/dynamodb-data-connector/actions

[codecov-badge]: https://codecov.io/gh/Funfunz/dynamodb-data-connector/branch/master/graph/badge.svg
[codecov]: https://codecov.io/gh/Funfunz/dynamodb-data-connector

[node]: https://img.shields.io/node/v/@funfunz/dynamodb-data-connector

[npm-badge]: https://img.shields.io/npm/v/@funfunz/dynamodb-data-connector?color=brightgreen
[npm]: https://www.npmjs.com/package/@funfunz/dynamodb-data-connector

[prs-badge]: https://img.shields.io/badge/PRs-welcome-brightgreen.svg
[prs]: http://makeapullrequest.com

[license-badge]: https://img.shields.io/github/license/JWebCoder/funfunz.svg
[license]: https://github.com/JWebCoder/funfunz/blob/master/LICENSE
npm package: @funfunz/json-data-connector
Description: json data connector for Funfunz
Author: João Leite
Latest version: 1.2.0

# Funfunz JSON Data Connector

[![Discord][discord-badge]][discord]
[![Build Status][actions-badge]][actions]
[![codecov][codecov-badge]][codecov]
![node][node]
[![npm version][npm-badge]][npm]
[![PRs Welcome][prs-badge]][prs]
[![GitHub][license-badge]][license]


## Features

This connector use a JSON file for each entity to storage its entries.


## Configuration

* `folderPath`: absolute path of the folder where this connector should read/write JSON files


### Example

```typescript
const config = {
  connectors: {
    mainDatabase: {
      type: '@funfunz/json-data-connector',
      config: {
        folderPath: path.join(__dirname, 'storage') 
      },
    }
  }
}
const funfunz = new Funfunz({ config, ... })
```


[discord-badge]: https://img.shields.io/discord/774439225520554004?logo=discord
[discord]: https://discord.gg/HwZ7zMJKwg

[actions-badge]: https://github.com/funfunz/json-data-connector/workflows/Node.js%20CI/badge.svg
[actions]: https://github.com/Funfunz/json-data-connector/actions

[codecov-badge]: https://codecov.io/gh/Funfunz/json-data-connector/branch/main/graph/badge.svg
[codecov]: https://codecov.io/gh/Funfunz/json-data-connector

[node]: https://img.shields.io/node/v/funfunz.svg

[npm-badge]: https://badge.fury.io/js/funfunz.svg
[npm]: https://badge.fury.io/js/funfunz

[prs-badge]: https://img.shields.io/badge/PRs-welcome-brightgreen.svg
[prs]: http://makeapullrequest.com

[license-badge]: https://img.shields.io/github/license/JWebCoder/funfunz.svg
[license]: https://github.com/JWebCoder/funfunz/blob/master/LICENSE
npm package: @funfunz/s3-data-connector
Description: s3 data connector for Funfunz
Author: João Moura
Latest version: 0.1.2

# Funfunz S3 Data Connector

[![Discord][discord-badge]][discord]
[![Build Status][actions-badge]][actions]
[![codecov][codecov-badge]][codecov]
![node][node]
[![npm version][npm-badge]][npm]
[![PRs Welcome][prs-badge]][prs]
[![GitHub][license-badge]][license]

This connector creates all the mutations and query to upload and retrieve files from an S3 bucket

At the moment, the connector is using the local machine AWS credentials

## Documentation

Just follow the [link](https://funfunz.github.io/funfunz/#/usage/dataConnectors/s3)

## Usage

**S3 config**

```js
{
  connectors: {
    [key: string]: { // user defined name for the connector
      type: '@funfunz/s3-data-connector',
      config: {
        bucket: string // name of the bucket
        region?: string // region of the bucket
        apiVersion?: string // api version to use
      },
    }
    ...
  }
}
```

**S3 entity**

```js
import { model } from '@funfunz/s3-data-connector'

export default model({
      name: 's3', // name for the entity, this will be visible under the GraphQL docs
      connector: 's3' // name defined by the user on the config file
    })
```


[discord-badge]: https://img.shields.io/discord/774439225520554004?logo=discord
[discord]: https://discord.gg/HwZ7zMJKwg

[actions-badge]: https://github.com/funfunz/s3-data-connector/workflows/Node.js%20CI/badge.svg
[actions]: https://github.com/Funfunz/s3-data-connector/actions

[codecov-badge]: https://codecov.io/gh/Funfunz/s3-data-connector/branch/master/graph/badge.svg
[codecov]: https://codecov.io/gh/Funfunz/s3-data-connector

[node]: https://img.shields.io/node/v/funfunz.svg

[npm-badge]: https://badge.fury.io/js/funfunz.svg
[npm]: https://badge.fury.io/js/funfunz

[prs-badge]: https://img.shields.io/badge/PRs-welcome-brightgreen.svg
[prs]: http://makeapullrequest.com

[license-badge]: https://img.shields.io/github/license/JWebCoder/funfunz.svg
[license]: https://github.com/JWebCoder/funfunz/blob/master/LICENSE
npm package: @funfunz/sql-data-connector
Description: sql data connector for Funfunz
Author: João Moura
Latest version: 0.12.1

# Funfunz SQL Data Connector

[![Discord][discord-badge]][discord]
[![Build Status][actions-badge]][actions]
[![codecov][codecov-badge]][codecov]
![node][node]
[![npm version][npm-badge]][npm]
[![PRs Welcome][prs-badge]][prs]
[![GitHub][license-badge]][license]

## Documentation

Just follow the [link](https://funfunz.github.io/funfunz/#/usage/dataConnectors/sql)

## Features

This connector uses KnexJS under the hood and is able to connect to SQL databases

**Supported Databases**

- Postgres
- MSSQL
- MySQL
- MariaDB
- SQLite3
- Oracle
- Amazon Redshift

The configuration supported for each of the databases can be checked at KnexJS

**Drivers required for each database**

- pg for PostgreSQL and Amazon Redshift
- mysql for MySQL or MariaDB
- sqlite3 for SQLite3
- mssql for MSSQL

[discord-badge]: https://img.shields.io/discord/774439225520554004?logo=discord
[discord]: https://discord.gg/HwZ7zMJKwg

[actions-badge]: https://github.com/funfunz/sql-data-connector/workflows/Node.js%20CI/badge.svg
[actions]: https://github.com/Funfunz/sql-data-connector/actions

[codecov-badge]: https://codecov.io/gh/Funfunz/sql-data-connector/branch/main/graph/badge.svg
[codecov]: https://codecov.io/gh/Funfunz/sql-data-connector

[node]: https://img.shields.io/node/v/funfunz.svg

[npm-badge]: https://badge.fury.io/js/funfunz.svg
[npm]: https://badge.fury.io/js/funfunz

[prs-badge]: https://img.shields.io/badge/PRs-welcome-brightgreen.svg
[prs]: http://makeapullrequest.com

[license-badge]: https://img.shields.io/github/license/JWebCoder/funfunz.svg
[license]: https://github.com/JWebCoder/funfunz/blob/master/LICENSE
npm package: @fungible-systems/native-module-test
Description: testing expo modules api
Author: Fungible Systems
Latest version: 0.1.0

# native-module-test

My new module

# API documentation

- [Documentation for the main branch](https://github.com/expo/expo/blob/main/docs/pages/versions/unversioned/sdk/native-module-test.md)
- [Documentation for the latest stable release](https://docs.expo.dev/versions/latest/sdk/native-module-test/)

# Installation in managed Expo projects

For [managed](https://docs.expo.dev/versions/latest/introduction/managed-vs-bare/) Expo projects, please follow the installation instructions in the [API documentation for the latest stable release](#api-documentation). If you follow the link and there is no documentation available then this library is not yet usable within managed projects &mdash; it is likely to be included in an upcoming Expo SDK release.

# Installation in bare React Native projects

For bare React Native projects, you must ensure that you have [installed and configured the `expo` package](https://docs.expo.dev/bare/installing-expo-modules/) before continuing.

### Add the package to your npm dependencies

```
npm install native-module-test
```

### Configure for iOS

Run `npx pod-install` after installing the npm package.


### Configure for Android



# Contributing

Contributions are very welcome! Please refer to guidelines described in the [contributing guide]( https://github.com/expo/expo#contributing).
npm package: @fungible-systems/react-native-expo-crypto
Description: implementation of crypto for React Native in expo
Author: Thomas Osmonson
Latest version: 0.0.1

# @fungible-systems/react-native-expo-crypto

> NOTE: this is a FORK of `https://github.com/themotu/react-native-expo-crypto`, with some modifications to update deps and enable `micro-stacks` usage for expo apps.

---

Note: this module is a clone of [crypto-browserify](https://github.com/crypto-browserify/crypto-browserify), with
randombytes replaced.

A port of node's `crypto` module to React Native.

## install

A typical workflow:

1. Install

  ```sh
  expo add expo-random && yarn add react-native-expo-crypto react-native-expo-bitcoinjs-lib
  ```

## the crypto in this box

What follows is unedited text from crypto-browserify

The goal of this module is to use expo-random for randombytes.

Here is the subset that is currently implemented:

* createHash (sha1, sha224, sha256, sha384, sha512, md5, rmd160)
* createHmac (sha1, sha224, sha256, sha384, sha512, md5, rmd160)
* pbkdf2
* pbkdf2Sync
* randomBytes
* pseudoRandomBytes
* createCipher (aes)
* createDecipher (aes)
* createDiffieHellman
* createSign (rsa, ecdsa)
* createVerify (rsa, ecdsa)
* createECDH (secp256k1)
* publicEncrypt/privateDecrypt (rsa)

## todo

these features from node's `crypto` are still unimplemented.

* createCredentials

these features would benefit from native implementations

* pbkdf2
* createSign
* createVerify
* createECDH
* publicEncrypto/privateDecrypt (rsa)

## contributions

If you are interested in writing a feature, please implement as a new module, which will be incorporated into
crypto-browserify as a dependency.

All deps must be compatible with node's crypto
(generate example inputs and outputs with node, and save base64 strings inside JSON, so that tests can run in the
browser. see [sha.js](https://github.com/dominictarr/sha.js)

Crypto is _extra serious_ so please do not hesitate to review the code, and post comments if you do.

## License

MIT
npm package: @fungible-systems/sip-12
Description: A simple TS / JS library for fetching vote data for [SIP 12](https://github.com/stacksgov/sips/pull/41).
Author: Hank Stoever
Latest version: 0.2.5

# `sip-12`

A simple TS / JS library for fetching vote data for [SIP 12](https://github.com/stacksgov/sips/pull/41).

## Setup

```bash
yarn add sip-12
# or npm
npm install --save sip-12
```

## Usage

### Get all vote data

```ts
import { getVoteData } from 'sip-12';
const data = await getVoteData();

// returns:
interface VoteData {
  votes: {
    support: Vote[];
    reject: Vote[];
  };
  totals: {
    support: bigint;
    reject: bigint;
  };
}
```

### Get BTC Vote transactions

```ts
import { getBTCVoteTransactions } from 'sip-12';

const approve = true;
const votes = await getBTCVoteTransactions(approve);

// returns:
interface VoteTransaction {
  stxAddress: string;
  txid: string;
  btcAddress: string;
  approve: boolean;
}
[];
```

### Get the amount of STX associated with a vote

The first input in the BTC transaction is either:

- The base58 version of a STX address (the stacker)
- The reward address of a stacker

The amount of STX associated with this address is fetched and added to a vote.

```ts
import { transformVote, transformVotes } from 'sip-12';

const voteTxs = await getBTCVoteTransactions(true);
const votes = await transformVotes(votes);

// or, for one vote
const vote = await transformVote(votes[0]);

// returns:
interface Vote extends VoteTransaction {
  amount: bigint;
}
```

### Get the BTC address used for voting

```ts
import { getVoteAddress, BTC_VOTE_ADDRESSES } from 'sip-12';

const yes = getVoteAddress(true);
// 111111111111111111112czxoHN
const no = getVoteAddress(false);
// 111111111111111111112kmzDG2

console.log(BTC_VOTE_ADDRESSES);
// { YES: yes, NO: no };
```
npm package: @fungifi/spore
Description: Core smart contracts of 🍄 FungiFi
Author: Kory Herzinger
Latest version: 0.0.2

# FungiFi Spore

Core smart contracts of 🍄 FungiFi

## Addresses

| Network       | Address                                    |
| ------------- | ------------------------------------------ |
| ***Görli***   | Not yet deployed                           |
| ***Kovan***   | Not yet deployed                           |
| ***Rinkeby*** | Not yet deployed                           |
| ***Mainnet*** | Not yet deployed                           |
| ***Ropsten*** | Not yet deployed                           |

## Requirements

* [NPM](https://nodejs.org/en/download/) >= 6.12.1
* [JQ](https://stedolan.github.io/jq/) >= 1.6

## Setup

### Clone the repo

```sh
$ git clone git@github.com:FungiFi/fungifi-spore.git
$ cd fungifi-spore
```

### Install dependencies

```sh
$ npm install
```

### Build the project

```sh
$ npm run build
```

### Run unit tests

```sh
$ npm run test
```

## Deploy

This project deploys the smart contracts to the Ethereum blockchain as well as publishing the NPM package whenever a release is cut from the repository in GitHub.

| Branch    | Network   | NPM Package Version |
|-----------|-----------|---------------------|
| `develop` | `ropsten` | `< 0.0.0`           |
| `main`    | `mainnet` | `>= 1.0.0`          |

### Test

| Repository Secret          | Description                           |
|----------------------------|---------------------------------------|
| `ROPSTEN_NETWORK_URL`      | The URL of the network provider node. |

To deploy and publish to test, create a release in GitHub off of the `develop` branch.

**IMPORTANT:** *For test releases, mark it as a "pre-release" before publishing, otherwise the workflow will not execute.*

### Production

| Repository Secret          | Description                           |
|----------------------------|---------------------------------------|
| `MAINNET_NETWORK_URL`      | The URL of the network provider node. |

To deploy and publish to production, create a release in GitHub off of the `main` branch.

**IMPORTANT:** *For production releases, DO NOT mark it as a "pre-release" before publishing, otherwise the workflow will not execute.*

## Configuration

### Local Accounts

For local development, test accounts are generated and funded with `100 ETH` from the Bip39 mnemonic:

`trust wait champion hero treat flush tip glow maid wear view record`

| HD Path            | Address                                      | Description           |
|--------------------| -------------------------------------------- | --------------------- |
| `m/44'/60'/0'/0/0` | `0x673834Dea22bDB68293c912277e5d35A2d24c33d` | The spore owner       |
| `m/44'/60'/0'/0/1` | `0xECCe1BDE07baaa263855eC463D99eD198ca74b70` | NFT seller            |
npm package: @fungifi/token
Description: The 🍄 FungiFi ERC20 utility token.
Author: Kory Herzinger
Latest version: 0.0.3

# FungiFi Token

FUNGI is a utility/governance token for the FungiFi system on the Ethereum blockchain. FUNGI tokens involve two basic value propositions for token holders:

1. FUNGI token holders have voting power in the governance of the FungiFi system and can steer the direction of the organization.
2. FUNGI token holders are entitled to dividends representing a portion of the fees generated by the FungiFi system.

## Addresses

| Network       | Address                                    |
| ------------- | ------------------------------------------ |
| ***Görli***   | Not yet deployed                           |
| ***Kovan***   | Not yet deployed                           |
| ***Rinkeby*** | Not yet deployed                           |
| ***Mainnet*** | Not yet deployed                           |
| ***Ropsten*** | Not yet deployed                           |

## Requirements

* [NPM](https://nodejs.org/en/download/) >= 6.12.1

## Setup

### Clone the repo

```sh
$ git clone git@github.com:FungiFi/fungifi-token.git
$ cd fungifi-token
```

### Install dependencies

```sh
$ npm install
```

### Build the project

```sh
$ npm run build
```

### Run unit tests

```sh
$ npm run test
```

## Deploy

This project deploys the smart contracts to the Ethereum blockchain as well as publishing the NPM package whenever a release is cut from the repository in GitHub.

| Branch    | Network   | NPM Package Version |
|-----------|-----------|---------------------|
| `develop` | `ropsten` | `< 0.0.0`           |
| `main`    | `mainnet` | `>= 1.0.0`          |

### Local network

???

### Testnet / Mainnet

???