type-fns
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions with SLSA provenance; this is a CI/CD migration, not a takeover. | ai | |
| phantom-deps | phantom-dep:domain-objects | AI (phantom-deps): Declared but not directly imported; likely used in config/type definitions only. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Husky git-hooks guard; only executes in git repos (dev environments), harmless for downstream consumers. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.21.3 | 2 / 35 | |
| 1.21.2 | 2 / 35 | |
| 1.21.1 | 3 / 35 | |
| 1.21.0 | 1 / 24 | |
| 1.20.2 | 1 / 24 |
v1.21.3
2 findingsThis version was published by a different npm account than previous versions on 2026-04-05. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.21.2
2 findingsThis version was published by a different npm account than previous versions on 2026-04-04. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.21.1
2 findingsThis version was published by a different npm account than previous versions on 2026-04-04. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.21.0
2 findingsScript: [ -d .git ] && npm run prepare:husky || exit 0
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.