@sisense/sdk-cli SEE LICENSE IN LICENSE.md 22 versions

@sisense/sdk-cli

npm Repository Homepage

Compose SDK package for interacting with Sisense via CLI

22

Versions

SEE LICENSE IN LICENSE.md

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

moti.sisensetuan.phamcompose-sdk-eng

Keywords

SisenseCompose SDK

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@sisense/sdk-common	AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic fires due to bundling, not a real missing import.	ai	2026/05/15
dependencies	unvetted-dep:node-window-polyfill	AI (dependencies): Standard browser-API polyfill for Node CLI use; stable and expected for this package.	ai	2026/05/15

Versions (showing 22 of 22)

Version	Deps	Published
2.28.0	11 / 8	2026-05-26
2.27.0	11 / 8	2026-05-14
2.24.0	10 / 8	2026-03-31
2.16.1	11 / 9	2025-12-12
2.16.0	11 / 9	2025-12-09
2.13.0	11 / 9	2025-10-29
2.12.0	11 / 9	2025-10-14
2.11.0	11 / 9	2025-09-30
2.10.0	11 / 9	2025-09-16
2.9.0	11 / 9	2025-09-02
2.8.0	11 / 9	2025-08-19
2.7.0	11 / 8	2025-08-05
2.6.0	11 / 8	2025-07-22
2.5.0	11 / 8	2025-07-09
2.4.1	11 / 8	2025-06-26
2.4.0	11 / 8	2025-06-25
2.3.1	11 / 8	2025-06-18
2.3.0	11 / 8	2025-06-11
2.2.0	11 / 8	2025-05-27
2.1.1	11 / 8	2025-05-21
2.1.0	11 / 8	2025-05-13
2.0.0	11 / 8	2025-04-30

v2.28.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.27.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.24.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.16.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.16.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.