@gooddata/sdk-backend-bear
GoodData Backend SPI implementation for the GoodData platform
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@gooddata/api-client-bear | AI (dependencies): First-party GoodData monorepo sibling, pinned exact version. | ai | |
| dependencies | unvetted-dep:@gooddata/api-model-bear | AI (dependencies): First-party GoodData monorepo sibling, pinned exact version. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Lockstep monorepo publish by trusted gooddata-ci; org-wide roster churn, not compromise. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Diff vs v9.9.0 shows no material change; dormancy is a registry-import gap, not new activity. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same lockstep monorepo roster churn as maintainer-added. | ai | |
| email-domain | unclaimed-email:rodri360.com | AI (email-domain): Stale contributor email metadata on a long-trusted monorepo package; not a takeover indicator here. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dep; stable FP for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 9.9.2 | 14 / 28 | |
| 9.9.1 | 14 / 28 | |
| 9.9.0 | 14 / 28 | |
| 9.6.0 | 14 / 28 |
v9.9.2
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. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.