open-index/open-npm huggingface dataset:
npm package: @pan-nft/bowie
Description: A CLI tool that will download the DB03 David Bowie photograph by Gavin Evans directly from Ethereum.
Author: Kai Davenport
Latest version: 1.0.0

# bowie

A CLI tool that will download the DB03 David Bowie photograph by Gavin Evans directly from Ethereum.

## install

```bash
npm install -g @pan-nft/bowie
```

## quick start

The quickest way to use this library is to just run it - it will download the image from Ethereum mainnet and write it to `Bowie DB03©Gavin Evans.jpg` in the current directory

```bash
$ pan-nft-bowie
downloaded image slice 0
downloaded image slice ...
downloaded image slice 24
written image to Bowie DB03©Gavin Evans.jpg
```

![Pan E Vision](https://storage.googleapis.com/pannft-files/website/assets/appimages/pan-e-vision.png)
![David Bowie DB03 by Gavin Evans](https://arweave.net/obCgK0z46Hu7ef960P9diSJweyZBVwYOn6LMl8Dt92o)

## usage

If you want to write the image to a different filename:

 * `--filename` = the filename to download the image to

If you want to connect to a different network and token - you should specify both the:

 * `--url` = the JSONRpc url of the network you want to connect to
 * `--contract` = the address of the token you want to download the image from

```bash
Usage: pan-nft-bowie [options]

Options:
  -V, --version              output the version number
  -u, --url <url>            The ethereum RPC URL to connect to (default: "https://mainnet.infura.io/v3/cab3c4baa4d64a77bf3a9413e90c81bd")
  -f, --filename <filename>  The file path to write to (default: "Bowie DB03©Gavin Evans.jpg")
  -c, --contract <contract>  The token contract to read from (default: "0xfb9f2821f9401b7f60d552d3883d5ee0732dad48")
  -h, --help                 output usage information
```
npm package: @pan-os/cerberus
Description: security wrapper to protect routes dynamically with heimdall structure
Author: Caio Alcantara
Latest version: 1.0.10

# Cerberus
[![wercker status](https://app.wercker.com/status/fab3b248ad74be9615d8af89d63f7e02/m/master "wercker status")](https://app.wercker.com/project/byKey/fab3b248ad74be9615d8af89d63f7e02)

A security wrapper to protect routes dynamically with Heimdall structure.

## Motivation
The whole idea behind this project is to split concerns betweens API structure to handle auth and strategies separately.

## Installation
TBD

### Requirements
TBD
* Restify


## Usage

```javascript
/**
 * Module Dependencies
 */
const { protect: withCerberus } = require('cerberus');
/**
 * Pseudo microservices
 */
const {
  terms, auth, config, user,
} = require('../services');

module.exports = (server) => {
  // Attach microservices to /
  Heimdall.attachMicroservice(server, withCerberus(config));
};

```

## Available Strategies
* Local Strategy (login, senha)
* GPlus
* Facebook

## Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

## License
[MIT](https://choosealicense.com/licenses/mit/)
npm package: @pan-os/heimdall
Description: A modular approach to add pseudo microservices organization into restify apps
Author: Pan Engineering
Latest version: 1.0.3

# Heimdall ![CI status](https://img.shields.io/badge/build-passing-brightgreen.svg)

An organizational and modular approach to handle pseudo microservices into restify applications.

## Motivation
The whole idea behind this project is to allow you to manage your API using a structure easy to maintain and split into several packages, heimdall wants to transform your mindset to microservices and help you to keep everything in place.

## Installation
`$ yarn add @pan-os/heimdall`

### Requirements
TBD
* Restify


## Usage

### Routes entrypoint

```javascript
/**
 * Module Dependencies
 */
const Heimdall = require('heimdall');
/**
 * Pseudo microservices
 */
const { user } = require('../services');

module.exports = (server) => {
  // Attach microservices to /
  Heimdall.attachMicroservice(server, user);
};
```

## Services folder structure

Represents your microservices

Example Service Structure
```javascript
// index.js

module.exports = [
  {
    method: 'post',
    path: '/user/register',
    action: (req, res, next) => { ... }
  }
];

// And you will be able to do a post to http://localhost:3000/user/register and 
// also should be able to manipulate/create your response into your action callback
```

## Development

```
$ yarn start:[env] (dev, prod)
```
## Contributors 🎉
Thanks goes out to all these wonderful people ([emoji key](https://github.com/kentcdodds/all-contributors#emoji-key)):

<!-- ALL-CONTRIBUTORS-LIST:START - Do not remove or modify this section -->
<!-- prettier-ignore -->
[<img src="https://avatars0.githubusercontent.com/u/17022606?s=460&v=4" width="100px;"/><br /><sub><b>Sérgio Freitas</b></sub>](https://github.com/sj-freitas)<br />

## Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

## License
[MIT](https://choosealicense.com/licenses/mit/)
npm package: @pan-ya/libgeo3dviewer
Description: In the project directory, you can run:
Latest version: 1.7.28

# README

## Available Scripts

In the project directory, you can run:

### `yarn dev`

Runs the app in the development mode.\
Open [http://localhost:3000](http://localhost:3000) to view it in the browser.

The page will reload if you make edits.\
You will also see any lint errors in the console.

### `yarn test`

Launches the test runner in the interactive watch mode.\
See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.

### `yarn build`

Builds the app for production to the `build` folder.\
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.\
Your app is ready to be deployed!

See the section about [deployment](https://facebook.github.io/create-react-app/docs/deployment) for more information.
npm package: @pan.codes/recipe-converter
Description: Web server for converting recipe URLs to JSON using recipe-parser
Latest version: 1.0.0

# Recipe Converter

A simple web server that converts recipe URLs into structured JSON data using the [@pan.codes/recipe-parser](../recipe-parser) package.

## Features

- Simple web UI for entering recipe URLs
- RESTful API for parsing recipes
- Supports any website with Schema.org structured data
- Returns structured JSON with ingredients, instructions, timing, and more

## Getting Started

### Installation

From the workspace root:

```bash
npm install
```

### Building

Build both projects:

```bash
npm run build
```

Or build just the converter:

```bash
npm run build:converter
```

### Running the Server

```bash
npm run start:converter
```

The server will start on `http://localhost:3000`

### Development Mode

To run with auto-reload during development:

```bash
npm run dev:converter
```

## API Endpoints

### POST /api/parse

Parse a recipe from a URL.

**Request Body:**
```json
{
  "url": "https://example.com/recipe"
}
```

**Response:**
```json
{
  "success": true,
  "data": {
    "name": "Recipe Name",
    "ingredients": [...],
    "instructions": [...],
    ...
  }
}
```

### GET /api/domains

Get list of supported domains (with custom parsers).

### GET /api/health

Health check endpoint.

## Web UI

Navigate to `http://localhost:3000` in your browser to use the simple web interface for converting recipe URLs to JSON.