@gooddata/sdk-backend-spi MIT 42 versions

@gooddata/sdk-backend-spi

npm Repository Homepage

GoodData Backend SPI abstraction interfaces

42

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

rodri360jaceksanivan.mjartanlupkotomas.kratochvilstanislavhackervojtasiipbenesgooddata-cinikolacechpetrjanuhung.caoxmortbich.nguyenno23reasonmatyas.kandltu.buimy.duonghang.ngoscavnickyjthao-luongthuong.nguyenhuyen.nguyennestor_encinastmuchkagdjanphong.nguyentuan.tran_gdmkoldusmartin.milickapjiranekmartozardavid.zoufalyvasek.zmrhallucy.doanhkad98hoaimylukas.therondrejvelisekgdamilietaandrenanninga-gooddatadusan-kovacik-profiqkhuongnguyenmatej.pavlikjenny_gooddataarmhajbertold8jyn.nguyenmara3londrej.macapetr.veprekjan.tychtl.gooddatatimurmuhjkbmmilan.dufekmaitrieuphilongjkbm_gdzdenekornstjiri.starobahenry.nguyen.gooddataadam.prchalfrankhuynhmacekondmartinnajpeter.kozasandrasuspjarjan.svager.gooddataminh.ho.gooddatamaiphuong.buijakubz_goodpavelcernymvarhalikhankadev

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): Long-established GoodData package; stale maintainer email is a hygiene issue, not an active takeover signal given the CI publisher track record.	ai	2026/05/17
dependencies	unvetted-dep:@gooddata/sdk-model	AI (dependencies): First-party GoodData monorepo sibling dependency; stable pattern across all versions of this package.	ai	2026/05/17
phantom-deps	phantom-dep:tslib	AI (phantom-deps): tslib is a known implicit runtime dep for TypeScript packages; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:ts-invariant	AI (phantom-deps): ts-invariant is listed as a direct dependency and referenced in config; phantom-dep is a false positive here.	ai	2026/04/29

Versions (showing 42 of 42)

Version	Deps	Published
11.40.0	4 / 23	2026-06-04
11.39.0	4 / 23	2026-05-28
11.38.0	4 / 23	2026-05-25
11.37.0	4 / 23	2026-05-25
11.36.0	4 / 23	2026-05-21
11.35.0	4 / 23	2026-05-14
11.34.0	4 / 23	2026-05-07
11.33.0	4 / 23	2026-05-07
11.32.0	4 / 23	2026-04-30
11.31.0	4 / 23	2026-04-23
11.30.0	4 / 23	2026-04-16
11.29.0	4 / 23	2026-04-10
11.28.0	4 / 23	2026-04-02
11.27.0	4 / 23	2026-03-26
11.26.0	4 / 23	2026-03-19
11.25.0	4 / 23	2026-03-12
11.24.0	4 / 23	2026-03-05
11.23.0	4 / 23	2026-02-26
11.22.0	4 / 23	2026-02-19
11.21.0	4 / 23	2026-02-12
11.20.0	4 / 23	2026-02-12
11.19.0	4 / 22	2026-02-06
11.18.0	4 / 23	2026-01-29
11.17.0	4 / 21	2026-01-22
11.16.0	4 / 21	2026-01-15
11.15.0	4 / 21	2026-01-08
11.14.0	4 / 21	2025-12-18
11.13.0	4 / 21	2025-12-11
11.12.0	4 / 21	2025-12-04
11.11.0	4 / 21	2025-11-27
11.10.0	4 / 21	2025-11-20
11.9.0	4 / 21	2025-11-13
11.8.0	4 / 21	2025-11-06
11.7.1	4 / 21	2025-11-03
11.7.0	4 / 21	2025-10-30
11.6.0	4 / 21	2025-10-23
11.5.0	4 / 21	2025-10-17
11.4.0	4 / 21	2025-10-10
11.3.0	4 / 23	2025-10-08
11.2.0	4 / 23	2025-10-02
11.1.0	4 / 23	2025-09-25
11.0.0	4 / 23	2025-09-22

v11.40.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.39.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.38.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.37.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.36.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.35.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.34.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.33.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.30.0

2 findings

HIGH Unclaimed maintainer email domain: rodri360.com email-domain

Maintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v11.29.0

2 findings

HIGH Unclaimed maintainer email domain: rodri360.com email-domain

Maintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v11.28.0

2 findings

HIGH Unclaimed maintainer email domain: rodri360.com email-domain

Maintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v11.27.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.26.0

2 findings

HIGH Unclaimed maintainer email domain: rodri360.com email-domain

Maintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v11.25.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.24.0

2 findings

HIGH Unclaimed maintainer email domain: rodri360.com email-domain

Maintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v11.23.0

2 findings

HIGH Unclaimed maintainer email domain: rodri360.com email-domain

Maintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v11.22.0

2 findings

HIGH Unclaimed maintainer email domain: rodri360.com email-domain

Maintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v11.21.0

2 findings

HIGH Unclaimed maintainer email domain: rodri360.com email-domain

Maintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v11.20.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.19.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.18.0

2 findings

HIGH Unclaimed maintainer email domain: rodri360.com email-domain

Maintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v11.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.16.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.15.0

2 findings

HIGH Unclaimed maintainer email domain: rodri360.com email-domain

Maintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v11.14.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.12.0

2 findings

HIGH Unclaimed maintainer email domain: rodri360.com email-domain

Maintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v11.11.0

2 findings

HIGH Unclaimed maintainer email domain: rodri360.com email-domain

Maintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v11.10.0

2 findings

HIGH Unclaimed maintainer email domain: rodri360.com email-domain

Maintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v11.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.8.0

2 findings

HIGH Unclaimed maintainer email domain: rodri360.com email-domain

Maintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.0.0

2 findings

HIGH Unclaimed maintainer email domain: rodri360.com email-domain

Maintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.