@sp-api-sdk/auth
Amazon Selling Partner API authentication package
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): Transition from manual publish (tusbar) to GitHub Actions CI/CD with SLSA attestation; legitimate automation change for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by CI/CD migration; SLSA attestation confirms legitimate publish pipeline. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 3.1.1 | 2 / 0 | |
| 3.1.0 | 2 / 0 | |
| 3.0.0 | 2 / 0 | |
| 2.2.25 | 2 / 0 | |
| 2.2.24 | 2 / 0 | |
| 2.2.23 | 2 / 0 | |
| 2.2.22 | 2 / 0 | |
| 2.2.21 | 2 / 0 | |
| 2.2.20 | 2 / 0 | |
| 2.2.19 | 2 / 0 | |
| 2.2.18 | 2 / 0 | |
| 2.2.15 | 2 / 0 | |
| 2.2.14 | 2 / 0 | |
| 2.2.13 | 2 / 0 | |
| 2.2.12 | 2 / 0 | |
| 2.2.11 | 2 / 0 | |
| 2.2.10 | 2 / 0 | |
| 2.2.9 | 2 / 0 | |
| 2.2.8 | 2 / 0 | |
| 2.2.7 | 2 / 0 | |
| 2.2.6 | 2 / 0 | |
| 2.2.5 | 2 / 0 | |
| 2.2.4 | 2 / 0 | |
| 2.2.3 | 2 / 0 | |
| 2.2.2 | 2 / 0 | |
| 2.2.1 | 2 / 0 | |
| 2.2.0 | 2 / 0 | |
| 2.1.4 | 2 / 0 | |
| 2.1.3 | 2 / 0 | |
| 2.1.2 | 2 / 0 | |
| 2.1.1 | 2 / 0 | |
| 2.1.0 | 2 / 0 | |
| 2.0.13 | 2 / 0 | |
| 2.0.12 | 2 / 0 | |
| 2.0.11 | 2 / 0 | |
| 2.0.10 | 2 / 0 | |
| 2.0.9 | 2 / 0 | |
| 2.0.8 | 2 / 0 |
v3.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.