@buildonspark/issuer-sdk
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@buildonspark/spark-sdk | AI (dependencies): Sibling package from the same org (@buildonspark); not an external unvetted dependency. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): ch-brian added within the @buildonspark org; consistent with normal team growth for this active SDK. | ai | |
| phantom-deps | phantom-dep:ts-proto | AI (phantom-deps): ts-proto is explicitly ignored in depcheck config; used for proto codegen, not a runtime import. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established SDK with 151 versions and real download volume; sparse README is a style choice, not spam. | ai | |
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): buffer is explicitly ignored in depcheck config; intentionally declared for browser polyfill use. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.1.35 | 4 / 16 | |
| 0.1.34 | 4 / 16 | |
| 0.1.8 | 4 / 16 | |
| 0.1.4 | 4 / 16 | |
| 0.0.100 | 4 / 16 | |
| 0.0.92 | 4 / 13 | |
| 0.0.85 | 8 / 13 | |
| 0.0.49 | 9 / 13 | |
| 0.0.47 | 9 / 13 | |
| 0.0.45 | 9 / 13 |
v0.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.49
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 (coreymartin) than the most recent previously approved version (cpartee6) on 2025-05-15, but coreymartin 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.47
2 findingsThis version was published by a different npm account than previous versions on 2025-05-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.