@gooddata/reference-workspace
GoodData SDK - Reference Workspace for tests
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
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): Package is published by gooddata-ci CI account with 430 approvals; stale maintainer email is low risk for this established org package. | ai | |
| provenance | no-provenance | AI (provenance): Large established monorepo package; lack of provenance is consistent across all versions and not a new signal. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime implicit dep in monorepo builds; stable false positive. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): lodash-es referenced in config files in this monorepo package; stable false positive. | ai | |
| phantom-deps | phantom-dep:@gooddata/sdk-backend-spi | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic unreliable for peer/type-only usage. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 11.49.0 | 4 / 20 | |
| 11.48.0 | 4 / 20 | |
| 11.47.0 | 4 / 20 | |
| 11.46.0 | 4 / 20 | |
| 11.45.0 | 4 / 20 | |
| 11.44.0 | 4 / 20 | |
| 11.43.0 | 4 / 20 | |
| 11.42.0 | 4 / 20 | |
| 11.41.0 | 4 / 20 | |
| 11.40.0 | 4 / 20 | |
| 11.39.0 | 4 / 20 | |
| 11.38.0 | 4 / 20 | |
| 11.37.0 | 4 / 20 | |
| 11.36.0 | 4 / 20 | |
| 11.35.0 | 4 / 20 | |
| 11.34.0 | 4 / 20 | |
| 11.33.0 | 4 / 20 | |
| 11.32.0 | 4 / 20 | |
| 11.31.0 | 4 / 20 | |
| 11.30.0 | 4 / 20 | |
| 11.29.0 | 4 / 20 | |
| 11.28.0 | 4 / 20 | |
| 11.27.0 | 4 / 20 | |
| 11.26.0 | 4 / 20 | |
| 11.25.0 | 4 / 20 | |
| 11.24.0 | 4 / 20 | |
| 11.23.0 | 4 / 20 | |
| 11.22.0 | 4 / 20 | |
| 11.21.0 | 4 / 20 | |
| 11.20.0 | 4 / 20 | |
| 11.19.0 | 4 / 20 | |
| 11.18.0 | 4 / 20 | |
| 11.17.0 | 4 / 19 | |
| 11.16.0 | 4 / 19 | |
| 11.15.0 | 4 / 19 | |
| 11.14.0 | 4 / 19 | |
| 11.13.0 | 4 / 19 | |
| 11.12.0 | 4 / 19 | |
| 11.11.0 | 4 / 19 | |
| 11.10.0 | 4 / 19 | |
| 11.9.0 | 4 / 19 | |
| 11.8.0 | 4 / 19 | |
| 11.7.1 | 4 / 19 |
v11.49.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.48.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.47.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.44.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.