← Home

@gooddata/api-client-tiger

npm Repository Homepage

API Client for GoodData Cloud and GoodData.CN

43
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

rodri360ivan.mjartanlupkotomas.kratochvilrodrigo.balsellsstanislavhackervojtasiipbenesgooddata-cinikolacechpetrjanuhung.caoxmortbich.nguyenno23reasonmatyas.kandlromanrakustu.buimy.duonghang.ngoscavnickyjthao-luongthuong.nguyenhuyen.nguyennestor_encinastmuchkagdjanphong.nguyentuan.tran_gdmkoldusmartin.milickapjiranekmartozardavid.zoufalyagrebnevs-gdvasek.zmrhalhkad98hoaimylukas.therondrejvelisekgdamilietaandrenanninga-gooddatapavelzrkilianchikdusan-kovacik-profiqkhuongnguyenmatej.pavlikjenny_gooddatagoodkubaarmhajbertold8jyn.nguyenmara3londrej.macapetr.veprekjan.tychtl.gooddatatimurmuhdanieldoktorjkbmmilan.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
source-diff obfuscated-file-transition:esm/endpoints/actions/index.d.ts AI (source-diff): Long single-line generated .d.ts export list, not true obfuscation. ai
maintainer-change maintainer-added AI (maintainer-change): Established CI publisher with large trusted history; routine team addition. ai
email-domain unclaimed-email:rodri360.com AI (email-domain): Long-established GoodData CI publisher with strong track record; stale maintainer email is low risk for this package. ai
dependencies unvetted-dep:@gooddata/sdk-model AI (dependencies): First-party GoodData monorepo sibling dependency; stable pattern across all versions of this package. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a declared runtime dependency in package.json; phantom-dep is a false positive here. ai
provenance no-provenance AI (provenance): Large established SDK monorepo; lack of provenance is consistent across all versions and not a risk signal here. ai

Versions (showing 43 of 43)

Version Deps Published
11.49.0 5 / 28
11.48.0 5 / 28
11.47.0 5 / 28
11.46.0 5 / 28
11.45.0 5 / 28
11.44.0 5 / 28
11.43.0 5 / 28
11.42.0 5 / 28
11.41.0 5 / 28
11.40.0 5 / 28
11.39.0 5 / 28
11.38.0 5 / 28
11.37.0 5 / 28
11.36.0 5 / 28
11.35.0 5 / 28
11.34.0 5 / 28
11.33.0 5 / 28
11.32.0 5 / 28
11.31.0 5 / 28
11.30.0 5 / 28
11.29.0 5 / 28
11.28.0 5 / 28
11.27.0 5 / 29
11.26.0 5 / 29
11.25.0 5 / 29
11.24.0 5 / 29
11.23.0 5 / 29
11.22.0 5 / 29
11.21.0 5 / 29
11.20.0 5 / 29
11.19.0 5 / 28
11.18.0 5 / 29
11.17.0 5 / 27
11.16.0 5 / 27
11.15.0 5 / 27
11.14.0 5 / 27
11.13.0 5 / 27
11.12.0 5 / 27
11.11.0 5 / 27
11.10.0 5 / 27
11.9.0 5 / 27
11.8.0 5 / 27
11.7.1 5 / 27

v11.49.0

2 findings
HIGH Modified file became obfuscated: esm/endpoints/actions/index.d.ts source-diff

This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.

INFO No provenance attestation provenance

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

v11.48.0

1 finding
INFO No provenance attestation provenance

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

v11.47.0

1 finding
INFO No provenance attestation provenance

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

v11.46.0

1 finding
INFO No provenance attestation provenance

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

v11.45.0

1 finding
INFO No provenance attestation provenance

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

v11.44.0

1 finding
INFO No provenance attestation provenance

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

v11.27.0

1 finding
INFO No provenance attestation provenance

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

v11.26.0

1 finding
INFO No provenance attestation provenance

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

v11.25.0

1 finding
INFO No provenance attestation provenance

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

v11.24.0

1 finding
INFO No provenance attestation provenance

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

v11.23.0

1 finding
INFO No provenance attestation provenance

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

v11.22.0

1 finding
INFO No provenance attestation provenance

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

v11.21.0

1 finding
INFO No provenance attestation provenance

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

v11.20.0

1 finding
INFO No provenance attestation provenance

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

v11.19.0

1 finding
INFO No provenance attestation provenance

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

v11.18.0

1 finding
INFO No provenance attestation provenance

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

v11.17.0

1 finding
INFO No provenance attestation provenance

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

v11.16.0

1 finding
INFO No provenance attestation provenance

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

v11.15.0

1 finding
INFO No provenance attestation provenance

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

v11.14.0

1 finding
INFO No provenance attestation provenance

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

v11.13.0

1 finding
INFO No provenance attestation provenance

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

v11.12.0

1 finding
INFO No provenance attestation provenance

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

v11.11.0

1 finding
INFO No provenance attestation provenance

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

v11.10.0

1 finding
INFO No provenance attestation provenance

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

v11.9.0

1 finding
INFO No provenance attestation provenance

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

v11.8.0

1 finding
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

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