@gooddata/sdk-ui-pluggable-application
GoodData SDK React helpers for pluggable applications
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): Maintainer email on a long-standing GoodData CI publisher; not the active publishing account and consistent across prior versions. | ai | |
| dependencies | unvetted-dep:@gooddata/sdk-backend-base | AI (dependencies): Sibling package from the same GoodData UI SDK monorepo release; versioned in lockstep. | ai | |
| dependencies | unvetted-dep:@gooddata/sdk-backend-tiger | AI (dependencies): Sibling package from the same GoodData UI SDK monorepo release; versioned in lockstep. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known TypeScript runtime implicit dependency; stable false positive for TS packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): SDK library in a large monorepo; sparse README and no keywords are expected for internal SDK packages. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 11.40.0 | 9 / 31 | |
| 11.39.0 | 9 / 31 | |
| 11.38.0 | 9 / 31 | |
| 11.37.0 | 9 / 31 | |
| 11.36.0 | 9 / 31 | |
| 11.35.0 | 9 / 31 | |
| 11.34.0 | 9 / 31 | |
| 11.33.0 | 9 / 31 | |
| 11.32.0 | 9 / 31 | |
| 11.31.0 | 10 / 31 | |
| 11.30.0 | 10 / 31 | |
| 11.29.0 | 10 / 31 | |
| 11.28.0 | 6 / 31 | |
| 11.27.0 | 3 / 31 | |
| 11.26.0 | 3 / 31 | |
| 11.25.0 | 3 / 31 |
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.31.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.30.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.29.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.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
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.26.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.25.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.