@1inch/limit-order-sdk
SDK for 1inch Limit Order Protocol
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): 1inch migrated publishing to GitHub Actions CI with SLSA attestation; consistent with org-level CI/CD adoption. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by SLSA-attested CI publish with no code changes; low takeover risk for this package. | ai | |
| dependencies | unvetted-dep:@1inch/byte-utils | AI (dependencies): Same-org dependency (@1inch) in a well-established SDK with SLSA provenance; stable false positive for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 5.3.0 | 2 / 26 | |
| 5.2.6 | 2 / 26 | |
| 5.2.5 | 2 / 26 | |
| 5.2.4 | 2 / 26 | |
| 5.2.3 | 2 / 26 | |
| 5.2.2 | 2 / 26 | |
| 5.2.1 | 2 / 26 | |
| 5.2.0 | 2 / 26 | |
| 5.1.0 | 2 / 26 | |
| 5.0.5 | 2 / 26 | |
| 5.0.4 | 2 / 26 | |
| 5.0.3 | 2 / 25 | |
| 5.0.2 | 2 / 25 | |
| 5.0.1 | 2 / 25 | |
| 5.0.0 | 2 / 25 |
v5.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.3
2 findingsThis version was published by a different npm account than previous versions on 2025-10-23. 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.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.