@1inch/fusion-sdk
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): SDK expansion with dual ESM/CJS build output; consistent with 1inch's known release patterns. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase attributable to dual-format build output (ESM + CJS) added in this release. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known TypeScript runtime helper; declared in dependencies and devDependencies, stable false positive for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 2.4.8 | 5 / 30 | |
| 2.4.7 | 5 / 30 | |
| 2.4.6 | 5 / 30 | |
| 2.4.5 | 5 / 30 | |
| 2.4.4 | 5 / 30 | |
| 2.4.1 | 5 / 30 | |
| 2.4.0 | 5 / 30 | |
| 2.3.8 | 5 / 30 | |
| 2.3.7 | 5 / 30 | |
| 2.3.6 | 5 / 30 | |
| 2.3.5 | 5 / 28 | |
| 2.3.4 | 5 / 28 | |
| 2.3.3 | 5 / 28 | |
| 2.3.2 | 5 / 28 | |
| 2.3.1 | 5 / 28 | |
| 2.3.0 | 5 / 28 | |
| 2.2.4 | 5 / 28 |
v2.4.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.