npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@coraprotocol/core

v0.2.5

Published

Cora contracts of the Cora Protocol

Readme

Cora Protocol Monorepo

Non liquidatable loans

Requirements

  • Node.js version 16.13.1 (we recommend getting nvm)

Getting Started

# change the node version 16.13.1
nvm use

# install dependencies
yarn 

Next you'll need to create a .env file. An example file .env.example is provided for you to use as a starting point. [submodule "modules/cora-governance-initiation"] path = modules/cora-governance-initiation url = https://github.com/Cora-Protocol/cora-governance-initiation.git branch = main

[submodule "lib/forge-std"] path = lib/forge-std url = https://github.com/foundry-rs/forge-std

Commands

yarn prepare:subgraph

yarn compile:protocol

yarn start:app

yarn start:storybook

Submodules

This repository uses other Cora repos as Git submodules.

They are located at modules, we include their Solidity files at contracts/modules

Create a submodule

git submodule add https://github.com/Cora-Protocol/<submodule_name>.git modules/<submodule_name>

Note that only the contracts from a submodule that are used in some way (e.g. inheritance) from these project contracts will be available as Hardhat artifacts. Otherwise, it can be imported here HardhatModulesArtifacts.sol which is just a dummy contract to make sure Hardhat will include the module contracts in the artifacts folder.

To clone the repo with submodules:

git clone https://github.com/Cora-Protocol/dev.git
git submodule update --init --recursive

Update submodules in this repo:

git submodule update --recursive --remote

To push changes to a submodule to its own repo:

cd [path/to/submodule]
git push
cd ..

Governance initiation

We are doing it in steps, facilitated by the scripts/governance_initiation/generateGovernanceInitiation.ts script.

  1. We deploy GovernanceInitiationData.sol