@gooddata/sdk-ui-all
GoodData SDK - All-In-One
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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:rodri360.com | AI (email-domain): Publisher is gooddata-ci CI account; the stale maintainer email is a legacy artifact, not the active publish identity. | ai | |
| dependencies | unvetted-dep:@gooddata/sdk-ui-ext | AI (dependencies): First-party monorepo sibling package; always released in lockstep with this package. | ai | |
| dependencies | unvetted-dep:@gooddata/sdk-ui-geo | AI (dependencies): First-party monorepo sibling package; always released in lockstep with this package. | ai | |
| dependencies | unvetted-dep:@gooddata/sdk-ui-pivot | AI (dependencies): First-party monorepo sibling package; always released in lockstep with this package. | ai | |
| dependencies | unvetted-dep:@gooddata/sdk-model | AI (dependencies): First-party monorepo sibling package; always released in lockstep with this package. | ai | |
| dependencies | unvetted-dep:@gooddata/sdk-ui-filters | AI (dependencies): First-party monorepo sibling package; always released in lockstep with this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a declared runtime dependency used implicitly by TypeScript compilation output; stable false positive. | ai | |
| dependencies | unvetted-dep:@gooddata/sdk-ui-charts | AI (dependencies): First-party monorepo sibling package; always released in lockstep with this package. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 11.40.0 | 9 / 22 | |
| 11.39.0 | 9 / 22 | |
| 11.38.0 | 9 / 22 | |
| 11.37.0 | 9 / 22 | |
| 11.36.0 | 9 / 22 | |
| 11.35.0 | 9 / 22 | |
| 11.34.0 | 9 / 22 | |
| 11.33.0 | 9 / 22 | |
| 11.32.0 | 9 / 22 | |
| 11.31.0 | 9 / 22 | |
| 11.30.0 | 9 / 22 | |
| 11.29.0 | 9 / 22 | |
| 11.28.0 | 9 / 22 | |
| 11.27.0 | 9 / 22 | |
| 11.26.0 | 9 / 22 | |
| 11.25.0 | 9 / 22 | |
| 11.24.0 | 9 / 22 | |
| 11.23.0 | 9 / 22 | |
| 11.22.0 | 9 / 22 | |
| 11.21.0 | 9 / 22 | |
| 11.20.0 | 9 / 22 | |
| 11.19.0 | 9 / 21 | |
| 11.18.0 | 9 / 21 | |
| 11.17.0 | 9 / 19 | |
| 11.16.0 | 9 / 19 | |
| 11.15.0 | 9 / 19 | |
| 11.14.0 | 9 / 19 | |
| 11.13.0 | 9 / 19 | |
| 11.12.0 | 9 / 19 | |
| 11.11.0 | 9 / 19 | |
| 11.10.0 | 9 / 19 | |
| 11.9.0 | 9 / 19 | |
| 11.8.0 | 9 / 19 | |
| 11.7.1 | 9 / 19 | |
| 11.7.0 | 9 / 19 | |
| 11.6.0 | 9 / 19 | |
| 11.5.0 | 9 / 19 | |
| 11.4.0 | 9 / 19 | |
| 11.3.0 | 9 / 21 | |
| 11.2.0 | 9 / 21 | |
| 11.1.0 | 9 / 21 | |
| 11.0.0 | 9 / 21 |
v11.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.28.0
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.10.0
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.0
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.