@sinch/sdk-core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@sinch/sms | AI (dependencies): First-party Sinch SDK monorepo package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@sinch/voice | AI (dependencies): First-party Sinch SDK monorepo package; stable pattern across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Established Sinch SDK publisher; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.5.0 | 8 / 0 | |
| 1.4.3 | 8 / 0 | |
| 1.4.2 | 8 / 0 | |
| 1.4.1 | 8 / 0 | |
| 1.4.0 | 8 / 0 | |
| 1.3.0 | 7 / 0 | |
| 1.2.1 | 7 / 0 | |
| 1.2.0 | 7 / 0 |
v1.5.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (hugo-rivas-sinch) than the most recent previously approved version (asein_sinch) on 2026-07-01, but hugo-rivas-sinch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.