@palmetto/solarflare-sdk
SDK for Scalable Notification Service for SMS, Email, Mobile-Push, and Webhooks
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@palmetto/result | AI (dependencies): First-party @palmetto sibling dependency; consistent with this package's ecosystem. | ai | |
| dependencies | unvetted-dep:@palmetto/base-sdk-client | AI (dependencies): First-party @palmetto sibling dependency; consistent with this package's ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): Internal corporate SDK; provenance attestation not yet adopted by this org, consistent across versions. | ai | |
| license | uncommon-license:UNLICENSED | AI (license): Intentionally proprietary internal SDK; UNLICENSED is expected for this package. | ai | |
| phantom-deps | phantom-dep:openapi-fetch | AI (phantom-deps): openapi-fetch is a declared runtime dep used in generated dist code; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 3 / 8 | |
| 0.6.11 | 3 / 8 | |
| 0.6.10 | 3 / 8 | |
| 0.6.9 | 3 / 8 | |
| 0.6.8 | 3 / 8 | |
| 0.6.7 | 3 / 8 | |
| 0.6.5 | 3 / 8 | |
| 0.6.4 | 3 / 8 | |
| 0.6.3 | 3 / 8 | |
| 0.6.1 | 3 / 8 | |
| 0.6.0 | 3 / 8 | |
| 0.5.1 | 3 / 8 | |
| 0.5.0 | 3 / 8 | |
| 0.4.0 | 3 / 8 | |
| 0.3.0 | 3 / 8 | |
| 0.1.1 | 3 / 8 | |
| 0.1.0 | 3 / 8 |
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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.