@gooddata/sdk-ui-catalog
GoodData SDK - Analytics Catalog
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine maintainer rotation within established GoodData org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): GoodData org rotation; publisher has strong track record with no rejections. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @joint/core and @joint/layout-directed-graph are established JointJS packages; addition is consistent with UI feature expansion. | ai | |
| email-domain | unclaimed-email:rodri360.com | AI (email-domain): Stale maintainer email; publishing is done via gooddata-ci with a clean track record, not this address. | ai | |
| phantom-deps | phantom-dep:@gooddata/sdk-ui-semantic-search | AI (phantom-deps): Same-org SDK sibling; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@gooddata/sdk-ui-theme-provider | AI (phantom-deps): Same-org SDK sibling; may be re-exported or used indirectly; stable false positive. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Build-time framework dep loaded by convention in GoodData SDK monorepo; stable false positive. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dep for TypeScript compiled output; stable false positive for this package. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 11.40.0 | 22 / 42 | |
| 11.39.0 | 22 / 42 | |
| 11.38.0 | 22 / 42 | |
| 11.37.0 | 22 / 42 | |
| 11.36.0 | 22 / 42 | |
| 11.35.0 | 22 / 42 | |
| 11.34.0 | 22 / 42 | |
| 11.33.0 | 22 / 42 | |
| 11.32.0 | 22 / 42 | |
| 11.31.0 | 22 / 42 | |
| 11.30.0 | 22 / 42 | |
| 11.29.0 | 22 / 42 | |
| 11.28.0 | 14 / 42 | |
| 11.27.0 | 14 / 42 | |
| 11.26.0 | 14 / 42 | |
| 11.25.0 | 14 / 42 | |
| 11.24.0 | 14 / 42 | |
| 11.23.0 | 14 / 42 | |
| 11.22.0 | 12 / 42 | |
| 11.21.0 | 11 / 42 | |
| 11.20.0 | 11 / 42 | |
| 11.19.0 | 11 / 41 | |
| 11.18.0 | 11 / 42 | |
| 11.17.0 | 11 / 40 | |
| 11.16.0 | 11 / 40 | |
| 11.15.0 | 11 / 40 | |
| 11.14.0 | 11 / 40 | |
| 11.13.0 | 11 / 40 | |
| 11.12.0 | 11 / 40 | |
| 11.11.0 | 11 / 40 | |
| 11.10.0 | 11 / 40 | |
| 11.9.0 | 11 / 40 | |
| 11.8.0 | 11 / 40 | |
| 11.7.1 | 11 / 40 | |
| 11.7.0 | 11 / 40 | |
| 11.6.0 | 11 / 40 | |
| 11.5.0 | 11 / 40 | |
| 11.4.0 | 11 / 40 | |
| 11.3.0 | 11 / 41 | |
| 11.2.0 | 11 / 41 | |
| 11.1.0 | 11 / 41 | |
| 11.0.0 | 11 / 41 |
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
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.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
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.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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.9.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.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.7.1
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.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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
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.