open-index/open-npm huggingface dataset:
npm package: @feedsnetwork/feeds-js-sdk
Description: FeedsNetwork social media NFT SDK
Latest version: 1.0.3

Feeds SDK
==========

Feeds has been a fully **decentralized** social network since its inception, and it need be oriented as a universal decentralized social networking service, not be confined to be pure application. With more third-parties integrated Feeds SDKs, a Feeds ecosystem would be brewed and risen with more traffic together.

### An use-case

Imagine a scenario where users can `mint` #Phantz NFTs, `discuss` #Phantz topics on their dedicated Feeds channel, and `trade` #Phantz NFTs on the Pasar marketplace. All activities are available on the #Phantz website. As a result, users will feel sticky and royal with the Phantz collection.

*With Feeds SDKs, Phantz website can integrate basic `social graph` and `channel service` onto Phantz website. Therefore, Phantz website can have it’s owned channels to dedicated discuss around `Phantz collection` on its website.  And plus being with Pasar market integrated on website, users would be more roylaty and sticky to Phantz project or product***

### Components

`Feeds SDK` contains a package of libraries to be integrated into third-party applications, which would be made up of three layers:

- Profile NFT

- Social Graph

- Feeds channel



`Social Graph` is the core component of `Feeds SDK` and `Social Graph` consist of the relationship graph between users. There are three dimensions of soical graph content:

- Generic soical graph:  `following relationship`
- Social graph related to `channel`
- Creative VCs-based social graph

With `social graph`  `SDKs` , applications can design their own soical features like ***Youtube*** or ***Reddit,*** but they would integrate `social graph` data into their application to gain basic user base.

Apart from `social graph` , Feeds has it’s own format standard of social data consisted of `#channel` and `#post` data.



## Build

Prepared that `nodejs`need to be installed on your local device, then clone  the repository with the commands:

```
$ git clone https://github.com/feedsnetwork/feeds-sdk
$ cd feeds-sdk
```

Then run the commands below to build sdk 

```
$ npm install
$ npm build
```



## Contribution

Any contributions  to this project would be highly appreciated, including

- building docs
- report bug and bugfix
- Suggestion or advices

The contribution acitivities can be either by creating an issue or pushing a pull request.

## 

## License

This project is licensed under the terms of the [MIT license](https://github.com/feedsnetwork/feeds-sdk/blob/master/LICENSE).
npm package: @feedspub/validators
Description: username, email and other validators for Feeds.pub
Author: timqian
Latest version: 0.0.8

# validators

A simple module(no dependency) to validate username, email and more for [Feeds Pub](https://feeds.pub).

Reusable on frontend and backend.

## Install

```bash
npm install validators
```

## Usage

```js
const { isEmail, isUsername, isPassword } = require('@feedspub/validators');

// true
isEmail('timqian@t9t.io');
isUsername('timqian');
isPassword('fidslde');
```

## Validating Rules

- email: `/\S+@\S+\.\S+/`
- username: `/^[a-zA-Z0-9\-\_]+$/`
- password: `length > 6`
npm package: @feedzai/analyzer-utilities
Description: Utilities for the repo-analyzer project
Author: Henrique Dias
Latest version: 1.0.47

# repo-analyzer-utilities

This repository contains several utilities used when creating metrics for [repo-analyzer](https://github.com/feedzai/repo-analyzer).

# Repository structure
- **Base.metric.js** contains the base class from which metrics should extend
- **utilities.js** contains several utility methods

# Licence

MIT
npm package: @feedzai/eslint-config-feedzai
Description: Feedzai's base JS ESLint extensible configuration
Author: Victor Fernandes
Latest version: 5.0.0

# eslint-config-feedzai

[![Build Status](https://travis-ci.com/feedzai/eslint-config-feedzai.svg?branch=master)](https://travis-ci.com/feedzai/eslint-config-feedzai)

This configuration contains our ESLint rules, including the ones for ECMAScript 6+. 
This packages requires `eslint` and `eslint-plugin-import`.

## Usage

### Installing package dependencies

In order to list the correct versions of each package you could use this command:

```shell
npm info "@feedzai/eslint-config-feedzai@latest" peerDependencies
```

After this command, you can install those packages manually or if you're using the **npm version > 5** you could use this shortcut:

```shell
npx install-peerdeps --dev @feedzai/eslint-config-feedzai
```

If you want to do all manually you should use:

```shell
npm install --save-dev @feedzai/eslint-config-feedzai eslint@^#.#.# eslint-plugin-import@^#.#.#
```

### Using Feedzai's ESLint configurations in your `.eslintrc` file

Add `"extends": "@feedzai/eslint-config-feedzai"`.

## Development tasks

You can check if this packages follow our coding style conventions by using `npm run lint`.

## Deployment tasks

The available commands are:

- `deploy:major` - creates a git tag and publish the X.0.0 version. _This command should be executed only in the `master` branch._
- `deploy:minor` - creates a git tag and publish the X.Y.0 version. _This command should be executed in the hot-fix branches (`hf-X.x.x`)._
- `deploy:patch` - creates a git tag and publish the X.Y.Z version. _This command should be executed in the hot-fix branches (`hf-X.x.x`)._
npm package: @feedzai/eslint-config-feedzai-react
Description: Feedzai's React ESLint extensible configuration
Author: Victor Fernandes
Latest version: 5.0.0

# eslint-config-feedzai-react

[![Build Status](https://travis-ci.com/feedzai/eslint-config-feedzai.svg?branch=master)](https://travis-ci.com/feedzai/eslint-config-feedzai)

This configuration extends the `@feedzai/eslint-config-feedzai` and includes the rules for React, a11y and Jest.
This package requires `eslint`, `@feedzai/eslint-config-feedzai`, `eslint-plugin-import`, `eslint-plugin-jest`, `eslint-plugin-jsx-a11y` and  `eslint-plugin-react`.

## Usage

### Installing package dependencies

In order to list the correct versions of each package you could use this command:

```shell
npm info "@feedzai/eslint-config-feedzai-react@latest" peerDependencies
```

After this command, you can install those packages manually or if you're using the **npm version > 5** you could use this shortcut:

```shell
npx install-peerdeps --dev @feedzai/eslint-config-feedzai-react
```

If you want to do all manually you should use:


```shell
npm install --save-dev @feedzai/eslint-config-feedzai-react eslint@^#.#.# @feedzai/eslint-config-feedzai@^#.#.# eslint-plugin-import@^#.#.# eslint-plugin-jest@^#.#.# eslint-plugin-jsx-a11y@^#.#.# eslint-plugin-react@^#.#.#
```

### Using Feedzai's ESLint configurations in your `.eslintrc` file

Add `"extends": "@feedzai/eslint-config-feedzai-react"`

## Development tasks

You can check if this packages follow our coding style conventions by using `npm run lint`.

## Deployment tasks

The available commands are:

- `deploy:major` - creates a git tag and publish the X.0.0 version. _This command should be executed only in the `master` branch._
- `deploy:minor` - creates a git tag and publish the X.Y.0 version. _This command should be executed in the hot-fix branches (`hf-X.x.x`)._
- `deploy:patch` - creates a git tag and publish the X.Y.Z version. _This command should be executed in the hot-fix branches (`hf-X.x.x`)._
npm package: @feedzai/feedzai-config
Description: Feedzai's config for repo-analyzer
Author: Henrique Dias
Latest version: 1.0.37

# repo-analyzer-config

Default configuration project for the [repo-analyzer](https://github.com/feedzai/repo-analyzer) tool.

# Metrics

This configuration implements the following metrics:
- **Bundle Size** Calculates the size of the generated `.js` and `.css` files. Assumes that an `npm run build` command exists and that it calls webpack. Works only with webpack.
- **Coverage** Calculates the branch and line coverage. Works only with jest.
- **Has build** Whenever the repository has a `npm run build` command
- **Has changelog** Whenever the repository has a CHANGELOG.md file
- **Has readme** Whenever the repository has a README.md file
- **Has test and linter** Whenever the repository has the `npm run test` and `npm run lint` commands
- **Ignored eslint rules** Counts the number of `eslint-disable`s
- **Custom eslint rules** Counts the number of rule overrides in the local eslint config.
- **Jest version** The version of Jest
- **React version** The version of React
- **React DOM version** The version of React DOM
- **Webpack version** The version of Webpack
- **Number of dependencies** The number of dependencies in `package.json`
- **Number of dev dependencies** The number of dev dependencies in `package.json`

# Other configurations

This repository also contains:
- Configurations to Elastic, namely the url/port (localhost:9200) and rate limiting.
- Configurations to the console, json and formatd file reporters.

# Extending this configuration

Take a look at the `index.js` file, the structure is simple.

If you implement new metrics we recommend overriding the `metrics` property and importing just the metrics you want.

If you need to override other properties we recommend cloning the object and changing what you need directly.

# Licence

MIT