@gearbox-protocol/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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher with SLSA attestation; legitimate automation change for this package. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Automated CI pipeline naturally produces rapid successive publishes; consistent with the SLSA-attested workflow. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Large SDK with 1769 versions; new source files reflect normal SDK growth, not injected code. | ai |
Versions (showing 7 of 207)
| Version | Deps | Published |
|---|---|---|
| 10.4.3 | 12 / 16 | |
| 10.4.2 | 12 / 16 | |
| 10.4.1 | 12 / 16 | |
| 10.4.0 | 12 / 16 | |
| 10.3.1 | 12 / 16 | |
| 10.3.0 | 12 / 16 | |
| 10.2.10 | 12 / 16 |
v10.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.