← Home

@gooddata/catalog-export

GoodData SDK Catalog Export tooling

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.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): oxfmt is a formatting tool used in lint/format scripts; no malicious signal. ai
dependencies unvetted-dep:@gooddata/sdk-model AI (dependencies): Same-org monorepo dependency pinned to matching version; stable pattern across all releases. ai
dependencies unvetted-dep:@gooddata/api-client-tiger AI (dependencies): Same-org monorepo dependency pinned to matching version; stable pattern across all releases. ai
email-domain unclaimed-email:rodri360.com AI (email-domain): Publisher is gooddata-ci CI account; the email is a stale maintainer contact, not the active publishing identity. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a known implicit runtime dependency for TypeScript packages; stable false positive. ai
phantom-deps phantom-dep:p-map AI (phantom-deps): Referenced in config files; phantom-dep heuristic fires on indirect usage patterns. ai
phantom-deps phantom-dep:@babel/plugin-transform-typescript AI (phantom-deps): Framework-scoped Babel plugin loaded by convention; stable false positive for this package. ai
phantom-deps phantom-dep:@gooddata/sdk-model AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for intra-monorepo packages. ai

Versions (showing 42 of 42)

Version Deps Published
11.40.0 16 / 24
11.39.0 16 / 24
11.38.0 16 / 24
11.37.0 16 / 24
11.36.0 16 / 24
11.35.0 16 / 24
11.34.0 16 / 24
11.33.0 16 / 24
11.32.0 16 / 24
11.31.0 16 / 24
11.30.0 16 / 24
11.29.0 16 / 24
11.28.0 16 / 24
11.27.0 16 / 24
11.26.0 16 / 24
11.25.0 16 / 24
11.24.0 16 / 24
11.23.0 16 / 24
11.22.0 16 / 24
11.21.0 16 / 24
11.20.0 16 / 24
11.19.0 16 / 24
11.18.0 16 / 24
11.17.0 16 / 23
11.16.0 16 / 23
11.15.0 16 / 23
11.14.0 16 / 23
11.13.0 16 / 23
11.12.0 16 / 23
11.11.0 16 / 23
11.10.0 16 / 23
11.9.0 16 / 23
11.8.0 16 / 23
11.7.1 16 / 23
11.7.0 16 / 23
11.6.0 16 / 23
11.5.0 16 / 23
11.4.0 16 / 23
11.3.0 16 / 25
11.2.0 16 / 24
11.1.0 16 / 24
11.0.0 16 / 24

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.32.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

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v11.23.0

1 finding
LOW No provenance attestation provenance

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

v11.22.0

1 finding
LOW No provenance attestation provenance

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

v11.21.0

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v11.11.0

1 finding
LOW No provenance attestation provenance

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v11.8.0

1 finding
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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v11.4.0

1 finding
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.3.0

1 finding
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.2.0

1 finding
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.1.0

1 finding
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.0.0

1 finding
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.