Is copy-own safe to use?

copy-own has no known vulnerabilities on the latest version (1.2.0). DepScope rates its health at 39/100 (critical risk).

What is the latest version of copy-own?

The latest version of copy-own is 1.2.0, released 2019-10-04.

Does copy-own have known vulnerabilities?

No known vulnerabilities on the latest version of copy-own.

Is copy-own deprecated?

No, copy-own is actively maintained. Latest release: 1.2.0 (2019-10-04).

What are alternatives to copy-own?

Popular alternatives to copy-own in npm include: minimatch, commander, eslint-visitor-keys, ajv, color-name.

What license does copy-own use?

copy-own is licensed under MIT.

copy-own

npmv1.2.0

Copies an object’s own properties to another object.

License MITpermissive3 versions1 maintainers0 deps

lamansky/copy-own

/ 100

Health

use with caution

[email protected] low health (39/100) — consider alternatives

Low health score (39/100)

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

0.4 KBminified

0.3 KB gzipped

0 direct dependencies

side effects

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/copy-own