open-index/open-npm huggingface dataset:
npm package: @justifi/webcomponents
Description: JustiFi Web Components
Latest version: 6.13.0

<p align="center">
  <a href="https://justifi.tech/" rel="noopener" target="_blank"><img width="150" height="133" src="https://justifi.tech/wp-content/uploads/2022/07/Light-BG-1.svg" alt="JustiFi logo"></a>
</p>

<h1 align="center">JustiFi Web Components</h1>

The JustiFi web component library is an ever-expanding repository of customizable, white-labeled fintech components. From Payment Forms and Tables/Lists to Charts and Onboarding Forms, this diverse collection is designed to empower our clients to seamlessly integrate crucial elements of their financial infrastructure into existing dashboards and software solutions.

## Installation

The best method for including the JustiFi web components in your application is via npm:

`npm install @justifi/webcomponents`

## Documentation

Visit [https://docs.justifi.tech/web-components/introduction](https://docs.justifi.tech/web-components/introduction) to view the full documentation.

## Examples

Our documentation features examples of rendered components.

- [Modular Checkout](https://docs.justifi.tech/web-components/modular-checkout/introduction)
- [Unified Fintech Checkout](https://docs.justifi.tech/web-components/payment-facilitation/unified-fintech-checkout%E2%84%A2)
- [Payment Provisioning](https://docs.justifi.tech/web-components/entities/payment-provisioning)

Visit our [documentation home page](https://docs.justifi.tech/web-components/introduction) to view examples of all available components.

## Questions and Issues

In order to best respond to questions and issues, we ask that users utilize the [Issue Section](https://github.com/justifi-tech/web-component-library/issues/new/choose) in the project's Github repo.

## Contributing

Read the [contributing guide](https://github.com/justifi-tech/web-component-library/blob/main/CONTRIBUTING.md) to learn about our development process, how to propose bug fixes and improvements, and how to build and test your changes.

## Changelog

The [changelog](https://github.com/justifi-tech/web-component-library/blob/main/packages/webcomponents/CHANGELOG.md) is regularly updated to reflect what's changed in each new release.
npm package: @justin-gee/rngcontracts
Description: CommitRevealRecover Random Number Generator Contracts
Author: Justin
Latest version: 0.0.1

# Bicorn-RX

Commit Reveal Recover Solidity PoC<br>
Random number generation in Titan (Layer 2)<br>

## INSTALL
```shell
yarn
```

## SET .env
```shell
ALCHEMY_MAINNET_RPC_URL=<GET_URL_FROM_https://dashboard.alchemy.com/>
MAINNET_RPC_URL=<GET_URL_FROM_https://app.infura.io/dashboard>
SEPOLIA_RPC_URL=<GET_URL_FROM_https://app.infura.io/dashboard>
ALCHEMY_SEPOLIA_RPC_URL=<GET_URL_FROM_https://dashboard.alchemy.com/>
POLYGON_MAINNET_RPC_URL=<GET_URL_FROM_https://app.infura.io/dashboard>
PRIVATE_KEY=<PRIVATE_KEY>
ETHERSCAN_API_KEY=<GET_KEY_FROM_https://etherscan.io/myapikey/>
REPORT_GAS=true
COINMARKETCAP_API_KEY=<GET_KEY_FROM_https://pro.coinmarketcap.com/account/>
```

## DEPLOYMENT

### to localhost
```shell
npx hardhat node
#Started HTTP and WebSocket JSON-RPC server at http://127.0.0.1:8545/

npx hardhat deploy --network localhost --tags CommitRevealRecoverRNG --reset
#deploying "CommitRevealRecoverRNG" (tx: 0xec0ed0faa71c54e85ecec9347227609b69acd980e00e35a1e3839bc71409b222)...: deployed at 0xe7f1725E7734CE288F8367e1Bb143E90bb3F0512 with 2821690 gas
```

### to target network
```shell
## CHANGE in hardhat.config.ts files at network :{} section
npx hardhat deploy --network <WRITE_YOUR_OWN_NETWORK_NAME> --tags CommitRevealRecoverRNG --reset
```

## TEST

### hardhat
```shell
#It runs test/CommitRevealRecoverRNG.test.ts
npx hardhat test test/CommitRevealRecoverRNG.test.ts --network hardhat
```

### localhost
```shell
#It runs test/CommitRevealRecoverRNG.test.ts
npx hardhat node
#Started HTTP and WebSocket JSON-RPC server at http://127.0.0.1:8545/
npx hardhat test test/CommitRevealRecoverRNG.test.ts --network localhost
```

## VERIFY CODE

- Guide(login required) : https://www.notion.so/onther/verify-contract-4b72acaa7e6c4dd0a8ee09fddfa6c539

### titan-goerli

```shell
npx hardhat verify <TARGET_ADDRESS> --network titangoerli
```

### titan

```shell
npx hardhat verify <TARGET_ADDRESS> --network titan
```
npm package: @justin-gee/uniswap-tokamak-hardhat-v3-deploy
Description: Hardhat plugin for Uniswap V3 solc ver 0.8 deployment
Author: EuiSin
Latest version: 1.0.7

# @uniswap/hardhat-v3-deploy

Deploy Uniswap V3 contracts in development.

## Installation

```sh
$ npm install @justin-gee/uniswap-tokamak-hardhat-v3-deploy
```

Import the plugin in your `hardhat.config.js`:

```js
require("@justin-gee/uniswap-tokamak-hardhat-v3-deploy");
```

Or if you are using TypeScript, in your `hardhat.config.ts`:

```ts
import "@justin-gee/uniswap-tokamak-hardhat-v3-deploy";
```

Now, run `npx hardhat` and you should see:

```
AVAILABLE TASKS:

  accounts      	Prints the list of accounts
  ...
  tokamak-uniswap-v3-deploy	Deploys Uniswap V3 contracts
  ...
  test          	Runs mocha tests
```

Great! Now, to deploy the contracts locally:

```sh
$ npx hardhat tokamak-uniswap-v3-deploy
```

After setting network to tokamakgoerli, deploy to tokamakgoerli

```sh
$ npx hardhat tokamak-uniswap-v3-deploy --network tokamakgoerli
```

And you're done. Time to build something great.

## Plugin Development

TODO
npm package: @justin8-cdk/alarms-stack
Description: This is a module to set up a very minimal SNS topic and subscribe a list of email addresses to receive alarms
Author: Justin Dray
Latest version: 1.3.0

# CDK Alarms Stack

This is a very short and simple wrapper to create an SNS topic and subscribe a list of email addresses to the topic. It is just a shorter and more readable form to insert in to a CDK app for use with CloudWatch alarms

# Usage

```
  const app = new cdk.App();
  const stack = new alarmsStack(app, "TestStack", {
      alarmEmails: ["me@example.com", "someoneElse@foo.xyz"],
      alarmsTopicName: "someTopic"
  });
```

The above will generate:

- An SNS topic named "someTopic"
- 2 email subscriptions, one for each of the given emails
- The alarm topic is accessible at `stack.alarmsTopic`
npm package: @justin8-cdk/logwrapper
Description: This module wraps basic settings for a CloudWatch log group; such as alarming on no logs or error messages in logs, along with subscribing to SNS topics for alarming
Author: Justin Dray
Latest version: 1.3.0

# CDK Log Wrapper

This module wraps basic settings for a CloudWatch log group; such as alarming on no logs or error messages in logs, along with subscribing to SNS topics for alarming.

## Usage

```typescript
const basicApp = new cdk.App();
const basicStack = new cdk.Stack(basicApp, "BasicStack");
const alarmsTopic = new Topic(basicStack, "topic");
const logGroupOne = new LogGroupWrapper(basicStack, "MyTestConstruct", {
  logGroupName: "/var/log/foo.log",
  alarmsTopic: alarmsTopic,
  filterPattern: FilterPattern.anyTerm("error", "Error"),
  noLogsAlarm: {
    enabled: true,
    evaluationPeriods: 5,
    metricPeriod: cdk.Duration.hours(1),
    threshold: 5,
  },
  errorsAlarm: {
    enabled: true,
    evaluationPeriods: 1,
    metricPeriod: cdk.Duration.minutes(5),
    threshold: 1,
  },
});
```

From the above:

- The named log group is created
- A metric filter is attached to filter on the given terms for errors/faults
- An alarm is created that will trigger when there are less than 5 lines of logs submitted to the log group in any 5 hour period
- An alarm is created that will trigger when there is one or more errors in the log file as determined by the given `filterPattern`
- The list of alarms is available at `logGroupOne.alarms`