open-index/open-npm huggingface dataset:
npm package: @orangemantis/fk-react-vanillae
Description: A react component library for Figma Plugins with Vanilla Extract CSS.
Author: Ron Sims II
Latest version: 0.2.1

## Installation

Install the package:

`npm install @orangemantis/fk-react-vanillae@latest`

## Setup

### CSS 

You can import the stylesheet form the `node_modules` directory:

`@import url('@orangemantis/fk-react-vanillae/dist/style.css');
`
npm package: @orangemantis/fk-utils
Description: Goodies for building Figma plugins.
Author: Ron Sims II
Latest version: 0.0.19

This package is is built purely using the Typescript compiler (TSC)

## Notes

When imorting this library into a Create React App (CRA), CRA may throw a source map error.  Look here for info on why this is not working: 
https://github.com/facebook/create-react-app/discussions/11767
npm package: @orangemug/oops
Description: Have I got a package version in my cache?
Latest version: 0.5.1

# `@orangemug/oops`

Have I got a package version in my npm/pnpm/yarn cache?

## Why?

I kept having to look up the CLI commands to check every time there was a npm package compromise, across the various package managers npm/pnpm/yarn.

This does that for me in one-shot and something I can share.

## Usage

Find out with `oops`

```bash
npx @orangemug/oops --help
# npx @orangemug/oops <dangerous_package_versions>
#
# Example: npx @orangemug/oops '@ctrl/tinycolor:4.1.1' '@ctrl/tinycolor:4.1.2'
```

You can attach this command to a bug tracker ticket somewhere in your company/organisation

> Check for compromised packages with
>
> ```bash
> npx @orangemug/oops \
>   '@ctrl/tinycolor:4.1.1' \
>   '@ctrl/tinycolor:4.1.2'
> ```

The examples are from <https://orca.security/resources/blog/npm-malware-campaign-tinycolor/>

It also support ranges such as `^4`

## Licence

MIT