← Home

is-type

npm Repository Homepage

Type checking from node core

2
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

juliangruber

Keywords

typecheckingisutiltypes

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Package is 12+ years old with ~200k weekly downloads; 0.0.0 reflects early npm conventions, not malicious intent. Stable false positive for this package. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance by many years; absence is expected and not a risk signal for this established package. ai

Versions (showing 2 of 2)

Version Deps Published
0.0.1 1 / 0
0.0.0 1 / 0

v0.0.1

1 finding
LOW No provenance attestation provenance

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

v0.0.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.