@sisense/sdk-plugins-dev
Compose SDK plugin development experience — DevApp, Vite plugin for Fusion, and deploy script
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 |
|---|---|---|---|---|
| license | uncommon-license:SEE LICENSE IN LICENSE.md | AI (license): Sisense proprietary license format; stable across all versions of this package family. | ai | |
| provenance | no-provenance | AI (provenance): Sisense org package; missing provenance is common and no other risk signals present. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.28.0 | 3 / 11 | |
| 2.27.0 | 3 / 11 | |
| 2.26.0 | 3 / 11 | |
| 2.25.0 | 3 / 11 | |
| 2.24.0 | 2 / 12 |
v2.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
1 finding[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.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.