fp-ts
Functional programming in TypeScript
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): fp-ts is a mature, high-trust package from its original author gcanti. Missing gitHead reflects a publish-environment change, not a supply-chain risk. | ai | |
| provenance | no-provenance | AI (provenance): fp-ts predates Sigstore provenance; absence is expected for this package's publish workflow. | ai |
Versions (showing 76 of 176)
| Version | Deps | Published |
|---|---|---|
| 1.15.0 | 0 / 24 | |
| 1.14.4 | 0 / 23 | |
| 1.14.3 | 0 / 21 | |
| 1.14.2 | 0 / 19 | |
| 1.14.1 | 0 / 19 | |
| 1.14.0 | 0 / 19 | |
| 1.13.0 | 0 / 19 | |
| 1.12.3 | 0 / 18 | |
| 1.12.2 | 0 / 18 | |
| 1.12.1 | 0 / 17 | |
| 1.12.0 | 0 / 17 | |
| 1.11.3 | 0 / 17 | |
| 1.11.2 | 0 / 17 | |
| 1.11.1 | 0 / 17 | |
| 1.11.0 | 0 / 17 | |
| 1.10.1 | 0 / 17 | |
| 1.10.0 | 0 / 16 | |
| 1.9.0 | 0 / 16 | |
| 1.8.1 | 0 / 16 | |
| 1.8.0 | 0 / 16 | |
| 1.7.1 | 0 / 16 | |
| 1.7.0 | 0 / 16 | |
| 1.6.2 | 0 / 16 | |
| 1.6.1 | 0 / 16 | |
| 1.6.0 | 0 / 16 | |
| 1.5.0 | 0 / 16 | |
| 1.4.1 | 0 / 17 | |
| 1.4.0 | 0 / 17 | |
| 1.3.0 | 0 / 17 | |
| 1.2.0 | 0 / 15 | |
| 1.1.0 | 0 / 15 | |
| 1.0.1 | 0 / 14 | |
| 1.0.0 | 0 / 14 | |
| 0.6.8 | 0 / 13 | |
| 0.6.7 | 0 / 13 | |
| 0.6.6 | 0 / 13 | |
| 0.6.5 | 0 / 12 | |
| 0.6.4 | 0 / 12 | |
| 0.6.3 | 0 / 13 | |
| 0.6.2 | 0 / 13 | |
| 0.6.1 | 0 / 13 | |
| 0.6.0 | 0 / 13 | |
| 0.5.4 | 0 / 8 | |
| 0.5.3 | 0 / 8 | |
| 0.5.2 | 0 / 8 | |
| 0.5.1 | 0 / 8 | |
| 0.5.0 | 0 / 8 | |
| 0.4.6 | 0 / 8 | |
| 0.4.5 | 0 / 8 | |
| 0.4.4 | 0 / 8 | |
| 0.4.3 | 0 / 8 | |
| 0.4.2 | 0 / 8 | |
| 0.4.1 | 0 / 8 | |
| 0.4.0 | 0 / 9 | |
| 0.3.5 | 0 / 9 | |
| 0.3.4 | 0 / 9 | |
| 0.3.3 | 0 / 9 | |
| 0.3.2 | 0 / 9 | |
| 0.3.1 | 0 / 9 | |
| 0.3.0 | 0 / 8 | |
| 0.2.9 | 1 / 8 | |
| 0.2.8 | 1 / 8 | |
| 0.2.7 | 1 / 8 | |
| 0.2.6 | 1 / 8 | |
| 0.2.5 | 1 / 8 | |
| 0.2.4 | 1 / 8 | |
| 0.2.3 | 1 / 8 | |
| 0.2.2 | 1 / 8 | |
| 0.2.1 | 1 / 8 | |
| 0.2.0 | 0 / 8 | |
| 0.1.1 | 0 / 7 | |
| 0.1.0 | 0 / 7 | |
| 0.0.4 | 0 / 7 | |
| 0.0.3 | 0 / 7 | |
| 0.0.2 | 0 / 5 | |
| 0.0.1 | 0 / 5 |
v1.15.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.
v1.14.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.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.
v1.13.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.
v1.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.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.
v1.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.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.
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.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.
v1.9.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.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.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.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.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.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.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.
v1.5.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.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.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.
v1.3.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.
v1.2.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.
v1.1.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.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.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.