@sp-api-sdk/solicitations-api-v1
With the Solicitations API you can build applications that send non-critical solicitations to buyers. You can get a list of solicitation types that are available for an order that you specify, then call an operation that sends a solicitation to the buyer
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 with SLSA attestation; consistent with monorepo automation migration. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects CI pipeline migration, not account takeover; SLSA attestation and repo continuity confirm legitimacy. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 4.1.1 | 2 / 0 | |
| 4.1.0 | 2 / 0 | |
| 4.0.0 | 2 / 0 | |
| 3.1.20 | 2 / 0 | |
| 3.1.19 | 2 / 0 | |
| 3.1.18 | 2 / 0 | |
| 3.1.17 | 2 / 0 | |
| 3.1.16 | 2 / 0 | |
| 3.1.15 | 2 / 0 | |
| 3.1.14 | 2 / 0 | |
| 3.1.13 | 2 / 0 | |
| 3.1.10 | 2 / 0 | |
| 3.1.9 | 2 / 0 | |
| 3.1.8 | 2 / 0 | |
| 3.1.7 | 2 / 0 | |
| 3.1.6 | 2 / 0 | |
| 3.1.5 | 2 / 0 | |
| 3.1.4 | 2 / 0 | |
| 3.1.3 | 2 / 0 | |
| 3.1.2 | 2 / 0 | |
| 3.1.1 | 2 / 0 | |
| 3.1.0 | 2 / 0 | |
| 3.0.1 | 2 / 0 | |
| 3.0.0 | 2 / 0 |
v4.1.1
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.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
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.