Is current-executing-script safe to use?

current-executing-script has no known vulnerabilities on the latest version (0.1.3). DepScope rates its health at 48/100 (high risk).

What is the latest version of current-executing-script?

The latest version of current-executing-script is 0.1.3, released 2015-12-27.

Does current-executing-script have known vulnerabilities?

No known vulnerabilities on the latest version of current-executing-script.

Is current-executing-script deprecated?

No, current-executing-script is actively maintained. Latest release: 0.1.3 (2015-12-27).

What are alternatives to current-executing-script?

Popular alternatives to current-executing-script in npm include: semver, ansi-styles, debug, minimatch, brace-expansion.

What license does current-executing-script use?

License information for current-executing-script is not declared in the registry metadata.

current-executing-script

npmv0.1.3

Get the currently executing script, regardless of its source/trigger/synchronicity. Similar to HTML5's `document.currentScript` but arguably much more useful!

4 versions1 maintainers0 deps5,870 weekly dl

JamesMGreene/currentExecutingScript

/ 100

Health

safe to use

[email protected] is safe to use (health: 48/100)

Health breakdown0 – 100

0/25

maintenance

6/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

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/current-executing-script