Is @types/source-map safe to use?

@types/source-map has no known vulnerabilities on the latest version (0.5.7). DepScope rates its health at 47/100 (high risk).

What is the latest version of @types/source-map?

The latest version of @types/source-map is 0.5.7, released 2018-01-02.

Does @types/source-map have known vulnerabilities?

No known vulnerabilities on the latest version of @types/source-map.

Is @types/source-map deprecated?

Yes, @types/source-map is deprecated: This is a stub types definition for source-map (https://github.com/mozilla/source-map). source-map provides its own type definitions, so you don't need @types/source-map installed! Consider using ? instead.

What are alternatives to @types/source-map?

Popular alternatives to @types/source-map in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does @types/source-map use?

@types/source-map is licensed under MIT.

@types/source-map

npmv0.5.7deprecated

Stub TypeScript definitions entry for source-map, which provides its own types definitions

License MITpermissive17 versions1 maintainers1 deps29,804 weekly dl

mozilla/source-map

/ 100

Health

find alternative

@types/source-map is deprecated — find an alternative

Moderate health score (47/100) — verify manually
Package is deprecated

Health breakdown0 – 100

20/25

maintenance

10/20

popularity

25/25

security

15/15

maturity

7/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

source-map

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@types/source-map