@sage-bionetworks/synapse-client
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
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.0.20 | 0 / 15 | |
| 0.0.19 | 0 / 15 | |
| 0.0.18 | 0 / 15 | |
| 0.0.15 | 0 / 15 | |
| 0.0.14 | 0 / 15 | |
| 0.0.13 | 0 / 15 | |
| 0.0.12 | 0 / 15 | |
| 0.0.11 | 0 / 15 |
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nickgros) than the most recent previously approved version (jay-hodgson) on 2026-07-21, but nickgros 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.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.