@palmetto/users-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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal SDK with 34 published versions; sparse README/metadata is a style choice, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all versions of this internal SDK; not a malice signal. | ai | |
| phantom-deps | phantom-dep:openapi-fetch | AI (phantom-deps): openapi-fetch is a runtime dep in package.json; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.9.1 | 4 / 8 | |
| 1.9.0 | 4 / 8 | |
| 1.8.4 | 4 / 8 | |
| 1.8.3 | 4 / 8 | |
| 1.8.2 | 4 / 8 | |
| 1.8.1 | 4 / 8 | |
| 1.8.0 | 4 / 8 | |
| 1.7.2 | 4 / 8 | |
| 1.7.1 | 4 / 8 | |
| 1.7.0 | 4 / 8 | |
| 1.5.1 | 4 / 8 | |
| 1.5.0 | 4 / 8 | |
| 1.3.0 | 4 / 8 | |
| 1.2.1 | 4 / 8 | |
| 1.2.0 | 4 / 8 | |
| 1.1.0 | 4 / 8 |
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.