@sp-api-sdk/notifications-api-v1
The Selling Partner API for Notifications lets you subscribe to notifications that are relevant to a selling partner's business. Using this API you can create a destination to receive notifications, subscribe to notifications, delete notification subscrip
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 4.2.1 | 2 / 0 | |
| 4.2.0 | 2 / 0 | |
| 4.1.0 | 2 / 0 | |
| 4.0.0 | 2 / 0 | |
| 3.0.22 | 2 / 0 | |
| 3.0.21 | 2 / 0 | |
| 3.0.20 | 2 / 0 | |
| 3.0.19 | 2 / 0 | |
| 3.0.18 | 2 / 0 | |
| 3.0.17 | 2 / 0 | |
| 3.0.16 | 2 / 0 | |
| 3.0.15 | 2 / 0 | |
| 3.0.12 | 2 / 0 | |
| 3.0.11 | 2 / 0 | |
| 3.0.10 | 2 / 0 | |
| 3.0.9 | 2 / 0 | |
| 3.0.8 | 2 / 0 | |
| 3.0.7 | 2 / 0 | |
| 3.0.6 | 2 / 0 | |
| 3.0.5 | 2 / 0 | |
| 3.0.4 | 2 / 0 | |
| 3.0.3 | 2 / 0 | |
| 3.0.2 | 2 / 0 | |
| 3.0.1 | 2 / 0 | |
| 3.0.0 | 2 / 0 |
v4.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.