← Home

feature-detect-es6

npm Repository Homepage
11
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

75lb

Keywords

detectes6featureclassarrow functionletarrayMapSetgeneratorpromisetemplate stringsymboldestructuringlanguagees2015spreaddefault parameter value

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff net-exec-file:index.js AI (source-diff): index.js uses eval() only on hardcoded ES6 syntax strings for feature detection — no network calls present. This is the library's core legitimate mechanism, stable across versions. ai
semgrep semgrep:eval-usage AI (semgrep): eval() is the intentional feature-detection mechanism, operating on hardcoded string literals like 'class Something {}'. No user-controlled input is ever passed to eval(). ai

Versions (showing 11 of 11)

Version Deps Published
1.5.0 1 / 2
1.4.1 1 / 2
1.4.0 1 / 2
1.3.1 1 / 2
1.3.0 1 / 2
1.2.0 1 / 2
1.1.0 0 / 2
1.0.0 0 / 2
0.2.0 0 / 2
0.1.1 0 / 2
0.1.0 0 / 2

v1.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.1

2 findings
HIGH New file with network + code execution: index.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.