@sisense/sdk-pivot-ui
Compose SDK package containing Pivot Table UI elements
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:raf | AI (phantom-deps): Bundled package; deps resolved at build time, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Bundled package; deps resolved at build time, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:immer | AI (phantom-deps): Bundled package; deps resolved at build time, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:dom-css | AI (phantom-deps): Bundled package; deps resolved at build time, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:dompurify | AI (phantom-deps): Bundled package; deps resolved at build time, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): Bundled package; deps resolved at build time, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Bundled package; deps resolved at build time, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:socket.io-client | AI (phantom-deps): Bundled package; deps resolved at build time, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@sisense/sdk-data | AI (phantom-deps): Same-org sibling package bundled at build time; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@sisense/sdk-common | AI (phantom-deps): Same-org sibling package bundled at build time; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@sisense/sdk-shared-ui | AI (phantom-deps): Same-org sibling package bundled at build time; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@sisense/sdk-rest-client | AI (phantom-deps): Same-org sibling package bundled at build time; stable false positive for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.28.0 | 13 / 21 | |
| 2.27.0 | 13 / 21 | |
| 2.26.0 | 13 / 21 | |
| 2.25.0 | 13 / 21 | |
| 2.24.0 | 13 / 21 | |
| 2.23.0 | 13 / 21 | |
| 2.22.0 | 13 / 21 | |
| 2.21.0 | 13 / 21 | |
| 2.20.0 | 13 / 21 | |
| 2.19.0 | 13 / 21 | |
| 2.18.1 | 13 / 21 | |
| 2.18.0 | 13 / 21 | |
| 2.17.0 | 13 / 21 |
v2.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.