@gooddata/sdk-ui
GoodData.UI SDK - 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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package; provenance absence is infrastructure-level, not version-specific risk. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): GoodData org team rotation; publisher account has 29 approved packages and clean history. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine team change within GoodData org, not indicative of takeover. | ai | |
| dependencies | unvetted-dep:@gooddata/number-formatter | AI (dependencies): GoodData-owned utility package; stable companion dependency across SDK releases. | ai | |
| dependencies | unvetted-dep:@gooddata/sdk-model | AI (dependencies): Same-org monorepo dependency released in lockstep; not an independent risk. | ai | |
| email-domain | unclaimed-email:rodri360.com | AI (email-domain): GoodData org package published via gooddata-ci CI account; stale personal email domain is low risk in this context. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dep; stable false positive for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 11.40.0 | 14 / 47 | |
| 11.37.0 | 14 / 47 | |
| 11.34.0 | 14 / 47 | |
| 11.33.0 | 14 / 47 | |
| 11.32.0 | 14 / 47 | |
| 11.31.0 | 14 / 47 | |
| 11.30.0 | 14 / 47 | |
| 11.29.0 | 14 / 47 | |
| 11.28.0 | 14 / 47 | |
| 11.23.0 | 14 / 47 | |
| 11.22.0 | 14 / 47 | |
| 11.19.0 | 14 / 46 | |
| 11.18.0 | 14 / 48 | |
| 11.16.0 | 14 / 46 | |
| 11.15.0 | 14 / 46 |
v11.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.37.0
1 finding[Accepted risk] Package 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 finding[Accepted risk] Package 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
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.