open-index/open-npm huggingface dataset:
npm package: @finnoto/fn-frontend-business
Description: for finnoto finnoto front end business layer logic
Latest version: 0.0.39

# @finnoto/fn-frontend-business

[![NPM](https://img.shields.io/npm/v/@finnoto/fn-frontend-business.svg)](https://www.npmjs.com/package/@finnoto/fn-frontend-business) [![JavaScript Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://standardjs.com)

## Install

```bash
yarn add @finnoto/fn-frontend-business
```

<!-- ## Usage -->

<!-- ```tsx
import React, { Component } from 'react'

import MyComponent from '@finnoto/fn-frontend-business'
import '@finnoto/fn-frontend-business/dist/index.css'

class Example extends Component {
  render() {
    return <MyComponent />
  }
}
``` -->

## License

MIT © [finnoto](https://github.com/finnoto)
npm package: @finnpauls/readme-badger
Description: Inserts badges into GitHub READMEs
Author: Andy Trevorah
Latest version: 1.0.0

readme-badger
=============

Temporary fork of https://github.com/gitterHQ/readme-badger

[![Build Status](https://travis-ci.org/gitterHQ/readme-badger.svg?branch=master)](https://travis-ci.org/gitterHQ/readme-badger)

Whizzy badges in your READMEs.

Install
-------

`npm install readme-badger`

How To Use
----------

### `addBadge(content, fileExt, imageUrl, linkUrl, altText)`

Returns the content but with a new badge inserted.

* `content`: the text content of a README.
* `fileExt`: the file extension of the README (md, textile, rdoc etc).
* `imageUrl`: the image url for the badge.
* `linkUrl`: the url for the badge to link to.
* `altText`: the alternative if images aren't visible. This will be used on its own for plaintext READMEs, so include a url in the text.

### `hasImageSupport(fileExt)`

Returns true/false depending on whether the format (`fileExt`) will render a badge image or just the altText.

* `fileExt`: the file extension of the README (md, textile, rdoc etc)

Example
-------
```javascript
var badger = require('readme-badger');

var readme = '# My Lovely Library\n' +
             '\n' +
             '## Features\n';
var imageUrl = 'https://badges.gitter.im/Join%20Chat.svg';
var linkUrl = 'https://gitter.im/gitterHQ/gitter';
var altText = 'Join the chat at https://gitter.im/gitterHQ/gitter';

var readmeWithBadge = badger.addBadge(readme, 'md', imageUrl, linkUrl, altText);

console.log(readmeWithBadge);
// # My Lovely Library
//
// [![Join the chat at https://gitter.im/gitterHQ/gitter](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/gitterHQ/gitter)
//
// ## Features
// ...

```

Format (`fileExt`) Support
--------------

readme-badger supports almost all of the [GitHub README markups](https://github.com/github/markup#markups):
* [markdown, mdown, mkdn, md](http://daringfireball.net/projects/markdown/)
* [textile](http://www.textism.com/tools/textile/)
* [rdoc](http://rdoc.sourceforge.net/)
* [org](http://orgmode.org/)
* [mediawiki, wiki](http://www.mediawiki.org/wiki/Help:Formatting)
* [rst](http://docutils.sourceforge.net/rst.html)
* [asciidoc, adoc, asc](http://asciidoc.org/)
* [pod](http://search.cpan.org/dist/perl/pod/perlpod.pod)

It will also failover to inserting the `altText` at the bottom of the README for any format that doesnt have image link support (creole, txt or anything else).

Building Locally
----------------

1. `git clone git@github.com:gitterHQ/readme-badger.git`
2. `cd readme-badger`
3. `npm install`
4. `npm test`

License
-------

MIT
npm package: @finnssmith/histoslider
Description: D3 based histogram slider component for React
Author: Finn Smith. Forked form Sam Hogg
Latest version: 1.1.1

# histoslider [![Circle CI](https://circleci.com/gh/samhogg/histoslider.svg?style=svg)](https://circleci.com/gh/samhogg/histoslider)

[![Greenkeeper badge](https://badges.greenkeeper.io/samhogg/histoslider.svg)](https://greenkeeper.io/)


## finnssmith Fork

A fork of https://github.com/samhogg/histoslider. 
- Updates the `react-motion` dependency to be compatible with React 16 and 17,
- Fixes the Histoslider for touch screens, where it was previously completely broken,
- Removes unused files, scripts, imports, and props.

## Original README

A D3 based histogram slider component for React. Useful for exploring distributions of things within data visualisations.

## Usage

`histoslider` has a few peer dependencies. Make sure these are installed before you go any further.

* `react`
* `react-dom`
* `d3-array`
* `d3-format`
* `d3-scale`

Then, to install,

`yarn add @finnssmith/histoslider`

Yay, glad we got that out of the way.

## Component API

```JSX
  <Histoslider
    // An array of objects to create the histogram
    data={[
      {
        x0: 0,    // Start of the bucket
        x: 1,     // End of the bucket
        y: 100    // Value
      },
      {
        x0: 1,    // Start of the bucket
        x: 2,     // End of the bucket
        y: 120    // Value
      },
      ...
    ]}
    // How much to pad the slider and histogram by, defaults to 20
    padding={20}
    // The extent of the selection, this doesn't have to be sorted (and you shouldn't sort it to store it)
    selection={[number, number]}
    // A function to handle a change in the selection
    onChange={array => { console.log(array) }}
  />
```

Check PropTypes for more options.
npm package: @fino314-oss/contract-scanner-mcp
Description: MCP server that scans Base L2 smart contracts for security risks. Detects mint/blacklist/backdoor/proxy patterns. Risk score 0-100.
Latest version: 1.0.0

# Contract Security Scanner — MCP Server

Scan any Base L2 smart contract for security risks directly from your AI assistant.

**3 tools exposed:**
- `scan_contract` — Full security scan (source verification, risky selectors, age, activity)
- `batch_scan` — Compare up to 5 contracts side by side
- `interpret_risk` — Get an actionable recommendation (SAFE / CAUTION / HIGH_RISK / DO_NOT_USE)

**Risk score: 0-100.** Analyzes: mint/blacklist/backdoor functions, proxy patterns, source verification, contract age, transaction activity.

---

## Installation

### Claude Desktop

Add to `~/Library/Application Support/Claude/claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "contract-scanner": {
      "command": "node",
      "args": ["/Users/sam/Desktop/samDev/p8/mcp/server.js"]
    }
  }
}
```

Restart Claude Desktop. The tools appear automatically.

---

### Cursor

Add to `.cursor/mcp.json` (project) or `~/.cursor/mcp.json` (global):

```json
{
  "mcpServers": {
    "contract-scanner": {
      "command": "node",
      "args": ["/Users/sam/Desktop/samDev/p8/mcp/server.js"]
    }
  }
}
```

---

### Cline (VS Code extension)

1. Open Cline settings → MCP Servers → Add server
2. Set type: `stdio`
3. Command: `node /Users/sam/Desktop/samDev/p8/mcp/server.js`

---

### Any MCP client (generic)

The server uses **stdio transport** — just pipe JSON-RPC messages:

```bash
node /Users/sam/Desktop/samDev/p8/mcp/server.js
```

---

## Usage examples

Once connected, just ask your AI assistant naturally:

```
"Scan this contract before I approve: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"

"Compare the risk of these 3 Aave clones: 0x... 0x... 0x..."

"Is this token safe to buy? 0x4ed4e862860bed51a9570b96d89af5e1b0efefed"
```

---

## What gets analyzed

| Check | Source |
|-------|--------|
| Source code verified? | BaseScan API |
| Mint / burn functions | Bytecode selector scan |
| Pause / freeze | Bytecode selector scan |
| Blacklist / whitelist | Bytecode selector scan |
| Backdoors (rescueTokens, withdrawAll) | Bytecode selector scan |
| Upgradeable proxy | BaseScan + delegatecall detection |
| Contract age | BaseScan transaction history |
| Activity level | BaseScan recent txs |

---

## Risk scoring

| Score | Label | Meaning |
|-------|-------|---------|
| 0-9 | SAFE | No red flags |
| 10-29 | LOW | Minor concerns |
| 30-49 | MEDIUM | Elevated risk — review before interacting |
| 50-69 | HIGH | Significant risk — small amounts only |
| 70+ | CRITICAL | Avoid — potential rug or backdoor |

---

## Technical notes

- **Chain**: Base L2 only (`https://mainnet.base.org`)
- **API**: BaseScan free tier (no key needed for basic checks; set `BASESCAN_API_KEY` env var for full source analysis)
- **No wallet needed**: read-only RPC calls only
- **Latency**: ~2-5s per contract (network dependent)

---

*Built on Base. Agent wallet: `0x804dd2cE4aA3296831c880139040e4326df13c6e`*
npm package: @finodigital/finoos-sdk
Description: TypeScript client for the finoOS2 REST API
Author: Fino Digital GmbH
Latest version: 1.1.2

# @finodigital/finoos-sdk

TypeScript client for the [finoOS2 REST API](https://os.fino.ai/docs/). Zero dependencies — uses native `fetch`, works in Node 22+, Deno, and edge runtimes.

## Install

```bash
npm install @finodigital/finoos-sdk
```

## Usage

```ts
import { FinoClient, getAccounts, getAllTransactions, getContracts } from "@finodigital/finoos-sdk";

const client = new FinoClient({
  baseUrl: "https://os.fino.cloud/api",
  clientId: "your-client-id",
  clientSecret: "your-client-secret",
});

await client.authenticate();

const accounts = await getAccounts(client, userId);
const transactions = await getAllTransactions(client, userId, { from: "2025-01-01" });
const contracts = await getContracts(client, userId);
```

## Features

- JWT authentication with auto-refresh (30s before expiry)
- Retry with full jitter backoff (max 3 retries for 429/5xx/network errors)
- Honours `Retry-After` header on 429 responses
- Typed error classes: `FinoApiError`, `FinoAuthError`, `FinoRateLimitError`, `FinoNotFoundError`, `FinoValidationError`, `FinoNetworkError`
- Full TypeScript types for all finoOS2 API resources
- ESM-only, zero dependencies

## API

### Client

- `new FinoClient(config)` — create a client with `{ baseUrl, clientId, clientSecret }`
- `client.authenticate()` — explicit auth (called automatically on first request)
- `client.request<T>(method, path, body?)` — typed HTTP request

### Endpoints

**Users:** `createUser`, `getUser`, `setUserScopes`, `triggerAnalysis`, `deleteUser`

**Banking:** `createConnectSession`, `createManagementSession`, `getAccounts`, `getTransactions`, `getAllTransactions`, `streamTransactions`, `triggerSync`, `getBankLogins`, `deleteBankLogin`, `disconnectAllBanking`

**Contracts:** `getContracts`

## License

MIT
npm package: @finoer/fino-cli
Description: The micro front framework tools
Author: fino
Latest version: 0.0.7

# finoer

The micro front framework tools

## 如何进行开发

> 安装依赖

```powershell
npm install
```


> 开发已经存在模版

- 在根目录下的tsconfing.json中的reference字段中确定需要监控的依赖包

  ```json
  // tsconfing.json
  {
    "references": [
        { "path": "./packages/finoer-core" }
     ]
  }
  ```

- 运行启动命令

  ```shell
  # 开发base模版
  npm run template:base
  # 其他模版项目, 在package.json中添加命令
  npm run template:other
  ```

> 开发package包

- 直接npm run dev <package名称>

  ```shell
  # 启动
  npm run dev finoer-core
  ```

- 打包 npm run build <package名称>

  ```shell
  # 打包
  npm run build finoer-core
  ```

- 生成文档npm run docs <package名称>

  ```shell
  # 打包
  npm run docs finoer-core
  ```

> 添加新的依赖包

1. 克隆/创建新的子模块

   ```powershell
   # 进入packages
   cd packages
   # 添加子模块
   git submodule add https://github.com/finoer/package-startup.git
   # 返回根目录
   cd ..
   ```

2. 根目录下tsconfig添加reference项目

   ```powershell
   {
       "compilerOptions": {
           // ...
       },
       "references": [
           {
               "path": "./packages/startup"
           }
       ]
   }
   ```

3. 运行启动命令

   ```powershell
   npm run template:<project>
   ```

4. 常见问题

   1. 没有监听到子模块的改变

      - 检查根项目下`tsconfig`下面reference是否已经包含了子模块

      - 检查子模块`package.json`入口是否正确

        ```
        {
        	"main": "dist/index.js",
        	"types": "dist/index.d.ts"
        }
        ```

      - 检查子模块的`tsconfig`文件如下属性是否正确

        ```json
         {
         		"compilerOptions": {
              "composite": true,
              "outDir": "./dist/", // 指定输出目录
              "baseUrl": "./src",
            }
         }
        ```

      



### 项目简介

....



### 项目目录

```js
core
├─templates // 微前端项目模版
|     ├─fino-child-vue // vue子项目模版
|     ├─fino-child // 子项目模版
|     ├─fino // 基座模版
├─src
|  └index.ts
├─scripts
|    ├─build.js
|    ├─dev.js
|    ├─docs.js
|    └utils.js
├─packages  // 项目依赖npm包
|    ├─finoer-core // 微前端框架主npm包
|    ├─finoer-component-vue // 子项目npm包

```



### 安装依赖

给package下面的npm包安装依赖

```
# npm run dev <包名>
npm run init finore-core 
# 或者
npm run init finoer-component-vue
```



### 启动命令

**运行packages下面的npm包**

```shell
# npm run dev <包名>
npm run dev finore-core 
# 或者
npm run dev finoer-component-vue
```


### 编译命令

```shell
# npm run build <包名>
npm run build finore-core 
# 或者
npm run build finoer-component-vue
```



### 生成文档

给package下的npm包生成文档

```
# npm run doc <包名>
npm run doc finore-core 
# 或者
npm run doc finoer-component-vue
```



![](./static/images/project.png)

## How to Run

```bash
git clone
git submodule update --init --recursive

```
npm package: @finoer/finoer-store
Description: > fino数据仓库
Latest version: 0.0.5

# fino-database 

> fino数据仓库

fino架构下的数据仓库， 用与管理fino子模块的数据和通信

### 1.  简介

1. 全局单例模式

1. 独立命名空间和代理

   fino数据仓库会按照子模块的名字创建一系列的命名空间， 

   为每个子模块设置单独的存储区域。

   同时，为了让开发人员更快，更友好的使用

   会把当前子模块的数据代理到根对象下面

   即

   ![3761](/Users/wangdongxu/Library/Application Support/typora-user-images/image-20201217114831097.png)

    所以开发人员的访问链条是这样的。

   $data.yueqi_module001.name

   但是fino-database做了一层代理， 代理之后的访问链条

   $data.name.

   即数据仓库会把当前模块的数据和全局数据代理到根访问链下。



2. 数据安全

   当前模块不允许修改其他模块的数据

   如当前在`yueqi_module001`下面

   是不允许修改其他模块的数据的。

   例如, 运行了如下代码

   ```js
   $data.data.jinzhao_module001.name = 123
   ```

   会被拦截

   

3.  数据监听

   可以通过监听方法坚挺到数据的改变

   

4. 设置全局方法和命名空间方法



5. 每个子模块的数据各自独立



6. 通过set设置的新数据会自动代理到跟访问连下面



1. 全局数据管理`global`

   可以通过

   ```js
   $data.set({key1: 1}, 'global')
   ```

   来给fino设置一个全局数据

   全局数据会被代理到数据仓库根prototype下面， 其他子模块可以通过

   ```js
   $data.key1
   ```

   访问全局数据

2. 其他子模块的数据
npm package: @finofo/react-international-phone
Description: ☎️ International phone input component for React
Author: Yurii Brusentsov
Latest version: 4.4.1

# react-international-phone

This is a fork of (https://github.com/goveo/react-international-phone)

🤙 International phone input component for React

![npm-version](https://img.shields.io/npm/v/react-international-phone)
![build-status-badge](https://img.shields.io/github/actions/workflow/status/goveo/react-international-phone/release.yml?branch=master)
![install-size-badge](https://badgen.net/packagephobia/install/react-international-phone)
[![codecov](https://codecov.io/gh/goveo/react-international-phone/branch/master/graph/badge.svg?token=SHEF4U216O)](https://codecov.io/gh/goveo/react-international-phone)
![downloads](https://img.shields.io/npm/dt/react-international-phone)
![Semantic Release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg)
[![stars](https://img.shields.io/github/stars/goveo/react-international-phone?style=social)](https://github.com/goveo/react-international-phone)

[Live demo: Storybook](https://react-international-phone-storybook.vercel.app)

![demo-gif](https://user-images.githubusercontent.com/25800848/215350455-0d362e64-d621-4856-a384-ab18d4a0d5fa.gif)

## Features

- 😎 **Easy to integrate** - Just import and use, no need for the initial setup. Integrate with any UI library using a headless hook.
- 🔍 **Country guessing** - Just start typing and the component will guess the country and format the phone. Country flags are rendered using [Twemoji](https://twemoji.twitter.com/).
- ✨ **Lightweight** - Low bundle size, no third-party dependencies.
- 🌈 **Easy to customize** - Customize styles and component behavior using props.
- ⌨ **Caret position handling** - Typing in the middle of the input, selection and deletion feels naturally.
- ✔️ **Validation** - Easily validate entered phone numbers using provided functions.

## Installation

```sh
$ npm i react-international-phone
```

## Basic usage

```tsx
import { useState } from 'react';
import { PhoneInput } from 'react-international-phone';
import 'react-international-phone/style.css';

const App = () => {
  const [phone, setPhone] = useState('');

  return (
    <div>
      <PhoneInput
        defaultCountry="ua"
        value={phone}
        onChange={(phone) => setPhone(phone)}
      />
    </div>
  );
};
```

## Documentation

Find the full API reference on [official documentation](https://react-international-phone-docs.vercel.app/).

## Migration

You can encounter some breaking changes after update between major versions.

Checkout migration documents that contain a list of breaking changes and ways to migrate:
<br/>
[Update from v3 to v4](https://react-international-phone-docs.vercel.app/docs/Migrations/migrate-to-v4)
<br/>
[Update from v2 to v3](https://react-international-phone-docs.vercel.app/docs/Migrations/migrate-to-v3)
<br/>
[Update from v1 to v2](https://react-international-phone-docs.vercel.app/docs/Migrations/migrate-to-v2)