# 1v

> NPM package name testing.

Latest version **1.0.0** (published 2019-11-21) · ISC license · 0 weekly downloads

> **Deprecated.** This package is deprecated.

## Install

```sh
npm install 1v
pnpm add 1v
yarn add 1v
bun add 1v
```

## Health

**Score 10/100 (F)** — status: deprecated.

Negative: deprecated.

## Facts

| | |
|---|---|
| Version | 1.0.0 |
| Published | 2019-11-21 |
| First published | 2019-11-21 |
| Weekly downloads | 0 |
| License | ISC |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 2 |
| Unpacked size | 2.2 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| Maintainers | dy |

## Links

- npm: https://www.npmjs.com/package/1v
- npm.io page: https://npm.io/package/1v

## Dependencies (2)

- [npm-name](https://npm.io/package/npm-name.md) ^5.5.0
- [all-the-package-names](https://npm.io/package/all-the-package-names.md) ^1.3903.0

## Recent versions

- 1.0.0 (latest) — 2019-11-21

## README

This package is mostly for discovering available npm names, because there are too many squatted good names, besides the other factors:

- NPM team sometimes violates NPM disputes rules, protecting squatters.
- Package name rules are uncertain, eg. `h-` etc.
- If you need this package name - mail me, that will be transfered faster than npm support.

Dear npm team: please clean up the registry from squatters, including this package. Thank you.

There's the script to list available package names.

---
_Source: https://npm.io/package/1v · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._