@sisense/sdk-ai-core
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/engines/dashboard-builder/dashboard-filters/filter-factory-types.d.ts | AI (source-diff): Long lines are TypeScript source embedded as string constants in .d.ts files for AI context; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/engines/dashboard-builder/dashboard-filters/measure-factory-types.d.ts | AI (source-diff): Same pattern: readable TS declarations embedded as string constants; not malicious obfuscation. | ai | |
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): Config/build tooling dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit TypeScript runtime dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Re-exported or used indirectly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:deepmerge | AI (phantom-deps): Re-exported or used indirectly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:partial-json | AI (phantom-deps): Re-exported or used indirectly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@faker-js/faker | AI (phantom-deps): Re-exported or used indirectly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:fast-deep-equal | AI (phantom-deps): Re-exported or used indirectly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:fast-json-patch | AI (phantom-deps): Re-exported or used indirectly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:zod-to-json-schema | AI (phantom-deps): Re-exported or used indirectly; stable pattern for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.10.1 | 13 / 8 | |
| 0.9.0 | 13 / 8 | |
| 0.8.0 | 13 / 8 | |
| 0.6.3 | 10 / 8 | |
| 0.6.2 | 10 / 8 | |
| 0.6.1 | 10 / 8 | |
| 0.6.0 | 10 / 8 | |
| 0.5.1 | 9 / 8 | |
| 0.5.0 | 9 / 8 | |
| 0.4.1 | 9 / 8 | |
| 0.4.0 | 9 / 8 | |
| 0.3.1 | 9 / 8 | |
| 0.3.0 | 9 / 8 | |
| 0.2.11 | 9 / 8 |
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.