is-function
is that thing a function? Use this module to find out
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Package has used version 0.0.0 for 12+ years with 4.3M weekly downloads; this is a stable, legitimate versioning choice, not a malicious throwaway pattern. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is due to a bundled browser test file (browser-test.js) for Testling cross-browser testing, consistent with the testling config in package.json. Not a runtime payload. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require calls are inside the bundled browser-test.js file, using browserify's integer module ID format — a standard bundling artifact, not malicious code. | ai | |
| provenance | no-provenance | AI (provenance): Package is 4489 days old and predates Sigstore provenance. Low risk given publisher track record and ecosystem trust. | ai |
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.