@sisense/sdk-pivot-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 — 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:react-use | AI (phantom-deps): Declared dependency used in bundled UI components; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:rc-tooltip | AI (phantom-deps): Declared dependency used in bundled UI components; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@emotion/cache | AI (phantom-deps): Declared dependency used in bundled UI components; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:react-custom-scrollbars | AI (phantom-deps): Declared dependency used in bundled UI components; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:raf | AI (phantom-deps): Declared dependency used in build/config; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Declared dependency used in build/config; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:immer | AI (phantom-deps): Declared dependency used in build/config; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Declared dependency used in build/config; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:dompurify | AI (phantom-deps): Declared dependency used in build/config; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): Declared dependency used in build/config; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:dom-css | AI (phantom-deps): Declared dependency used in build/config; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:socket.io-client | AI (phantom-deps): Declared dependency used in build/config; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@sisense/sdk-common | AI (phantom-deps): Declared sibling dependency in same org monorepo; stable pattern. | ai | |
| phantom-deps | phantom-dep:@sisense/sdk-shared-ui | AI (phantom-deps): Declared sibling dependency in same org monorepo; stable pattern. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 2.16.1 | 12 / 21 | |
| 2.16.0 | 11 / 21 | |
| 2.15.0 | 11 / 21 | |
| 2.14.0 | 11 / 21 | |
| 2.13.0 | 10 / 21 | |
| 2.12.0 | 10 / 21 | |
| 2.11.0 | 10 / 20 | |
| 2.10.0 | 10 / 20 | |
| 2.9.0 | 10 / 20 | |
| 2.8.0 | 10 / 20 | |
| 2.7.0 | 10 / 20 | |
| 2.6.0 | 10 / 20 | |
| 2.5.0 | 10 / 20 | |
| 2.4.1 | 10 / 20 | |
| 2.4.0 | 10 / 20 | |
| 2.3.1 | 10 / 20 | |
| 2.3.0 | 10 / 20 | |
| 2.2.0 | 17 / 19 | |
| 2.1.1 | 17 / 19 | |
| 2.1.0 | 17 / 19 |
v2.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.