@carto/api-client No license 39 versions

@carto/api-client

npm Repository Homepage

39

Versions

—

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

jmtorrescartodbjuanra-cartocartodbshylpxjaragonaaranadevzbiggjosmorsotvmilanfelixpalmermoicalcobaalmonacidjmgayamenusal

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:build/worker-compat.js	AI (source-diff): esbuild/tsup bundler output (visible __commonJS/__toESM preamble), not obfuscation.	ai	2026/07/16
phantom-deps	phantom-dep:@types/geojson	AI (phantom-deps): @types/geojson is a TypeScript type package used as a runtime dep for type exports; not a real phantom dep for this package.	ai	2026/05/01

Versions (showing 39 of 39)

Version	Deps	Published
0.5.31	7 / 51	2026-06-25
0.5.30	7 / 51	2026-06-24
0.5.29	7 / 51	2026-05-12
0.5.28	7 / 51	2026-05-06
0.5.27	7 / 51	2026-04-30
0.5.26	7 / 51	2026-03-25
0.5.25	7 / 51	2026-03-23
0.5.24	7 / 51	2026-01-14
0.5.23	7 / 51	2025-12-22
0.5.5	6 / 53	2025-05-20
0.5.4	6 / 53	2025-05-16
0.5.3	6 / 53	2025-05-13
0.5.2	6 / 53	2025-05-02
0.4.9	13 / 41	2025-03-14
0.4.8	12 / 37	2025-03-06
0.4.7	12 / 37	2025-03-05
0.4.6	6 / 29	2025-02-04
0.4.5	6 / 29	2025-01-14
0.4.4	6 / 38	2025-01-03
0.4.3	6 / 38	2024-12-30
0.4.2	6 / 38	2024-12-19
0.4.1	6 / 38	2024-12-12
0.4.0	6 / 38	2024-12-04
0.3.1	7 / 37	2024-10-08
0.3.0	7 / 37	2024-10-07
0.2.2	6 / 38	2024-10-03
0.2.1	6 / 38	2024-10-02
0.2.0	6 / 37	2024-09-27
0.1.1	6 / 37	2024-09-25
0.1.0	0 / 37	2024-09-05
0.0.44	0 / 37	2024-09-03
0.0.43	0 / 37	2024-08-29
0.0.42	0 / 37	2024-08-22
0.0.41	0 / 37	2024-07-24
0.0.39	0 / 37	2024-07-24
0.0.37	0 / 37	2024-07-24
0.0.35	0 / 37	2024-07-03
0.0.32	0 / 37	2024-07-01
0.0.30	0 / 37	2024-07-01

v0.5.26

2 findings

HIGH New obfuscated file: build/worker-compat.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.5.25

2 findings

HIGH New obfuscated file: build/worker-compat.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.5.24

2 findings

HIGH New obfuscated file: build/worker-compat.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.5.23

2 findings

HIGH New obfuscated file: build/worker-compat.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.4.9

1 finding

LOW No provenance attestation provenance

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

v0.4.8

1 finding

LOW No provenance attestation provenance

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

v0.4.7

1 finding

LOW No provenance attestation provenance

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

v0.4.6

1 finding

LOW No provenance attestation provenance

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

v0.4.5

1 finding

LOW No provenance attestation provenance

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

v0.4.4

1 finding

LOW No provenance attestation provenance

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

v0.4.3

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

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.

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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

v0.0.44

1 finding

LOW No provenance attestation provenance

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

v0.0.43

1 finding

LOW No provenance attestation provenance

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

v0.0.42

1 finding

LOW No provenance attestation provenance

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

v0.0.41

1 finding

LOW No provenance attestation provenance

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

v0.0.39

1 finding

LOW No provenance attestation provenance

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

v0.0.37

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.

v0.0.35

1 finding

LOW No provenance attestation provenance

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

v0.0.32

1 finding

LOW No provenance attestation provenance

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

v0.0.30

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.