@carto/ps-react-maps MIT 49 versions

@carto/ps-react-maps

npm Repository Homepage

CARTO's Professional Service React DeckGL library

49

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jmtorrescartodbjuanra-cartocartodbshylpxjaragonaaranadevzbiggjosmorsotvmilanfelixpalmermoicalcobaalmonacidjmgayamenusal

Keywords

cartopsreactdeckgl

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/assets/worker-CDL4vKo-.js	AI (source-diff): Minified Vite build output; sample shows geo/tile math only, no malicious patterns.	ai	2026/05/18
source-diff	obfuscated-file:dist/assets/worker-BYcCofGn.js	AI (source-diff): Vite-bundled minified worker with matching .js.map; content is standard tile/geo math, not obfuscated malware.	ai	2026/05/08
source-diff	obfuscated-file:dist/assets/worker-DeESwOs7.js	AI (source-diff): Minified Vite build output with source maps; geo/tile math content, no malicious patterns.	ai	2026/05/08

Versions (showing 49 of 49)

Version	Deps	Published
4.13.0	0 / 24	2026-05-21
4.12.0	0 / 24	2026-05-20
4.11.5	0 / 24	2026-05-19
4.11.4	0 / 24	2026-05-19
4.11.3	0 / 24	2026-05-18
4.11.2	0 / 24	2026-05-18
4.11.0	0 / 24	2026-05-04
4.10.0	0 / 24	2026-04-30
4.9.7	0 / 24	2026-04-20
4.9.6	0 / 24	2026-04-17
4.9.5	0 / 24	2026-04-15
4.9.4	0 / 24	2026-04-15
4.9.3	0 / 24	2026-03-30
4.9.2	0 / 24	2026-03-25
4.9.1	0 / 24	2026-03-19
4.9.0	0 / 24	2026-03-06
4.8.5	0 / 24	2026-02-20
4.8.4	0 / 24	2026-02-16
4.8.3	0 / 24	2026-02-11
4.8.2	0 / 23	2026-02-11
4.8.1	0 / 23	2026-02-10
4.8.0	0 / 23	2026-02-09
4.7.5	0 / 23	2026-02-02
4.7.4	0 / 23	2026-01-22
4.7.3	0 / 23	2026-01-22
4.7.2	0 / 23	2026-01-22
4.7.1	0 / 23	2025-12-12
4.7.0	0 / 23	2025-12-01
4.6.2	0 / 23	2025-11-10
4.6.1	0 / 23	2025-10-29
4.6.0	0 / 23	2025-10-27
4.5.2	0 / 23	2025-10-21
4.5.1	0 / 23	2025-10-14
4.5.0	0 / 23	2025-10-14
4.4.0	0 / 23	2025-10-07
4.3.1	0 / 23	2025-10-03
4.3.0	0 / 23	2025-10-02
4.2.6	0 / 23	2025-10-02
4.2.5	0 / 23	2025-09-29
4.2.4	0 / 23	2025-09-24
4.2.3	0 / 23	2025-09-24
4.2.2	0 / 23	2025-09-23
4.2.1	0 / 23	2025-09-18
4.2.0	0 / 23	2025-09-18
4.1.0	0 / 23	2025-09-18
4.0.3	0 / 23	2025-09-16
4.0.2	0 / 23	2025-09-15
4.0.1	0 / 23	2025-09-12
4.0.0	0 / 23	2025-09-12

v4.13.0

1 finding

LOW No provenance attestation provenance

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

v4.12.0

1 finding

LOW No provenance attestation provenance

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

v4.11.5

1 finding

LOW No provenance attestation provenance

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

v4.11.4

1 finding

LOW No provenance attestation provenance

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

v4.11.3

1 finding

LOW No provenance attestation provenance

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

v4.11.2

1 finding

LOW No provenance attestation provenance

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

v4.11.0

1 finding

LOW No provenance attestation provenance

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

v4.10.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.

v4.9.7

1 finding

LOW No provenance attestation provenance

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

v4.9.6

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.

v4.9.5

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.

v4.9.4

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.

v4.9.3

2 findings

HIGH New obfuscated file: dist/assets/worker-BYcCofGn.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.

v4.9.2

2 findings

HIGH New obfuscated file: dist/assets/worker-BYcCofGn.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.

v4.9.1

2 findings

HIGH New obfuscated file: dist/assets/worker-BYcCofGn.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.

v4.9.0

2 findings

HIGH New obfuscated file: dist/assets/worker-BYcCofGn.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.

v4.8.5

2 findings

HIGH New obfuscated file: dist/assets/worker-BYcCofGn.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.

v4.8.4

2 findings

HIGH New obfuscated file: dist/assets/worker-BYcCofGn.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.

v4.8.3

2 findings

HIGH New obfuscated file: dist/assets/worker-BYcCofGn.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.

v4.8.2

2 findings

HIGH New obfuscated file: dist/assets/worker-BYcCofGn.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.

v4.8.1

2 findings

HIGH New obfuscated file: dist/assets/worker-DeESwOs7.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.

v4.8.0

2 findings

HIGH New obfuscated file: dist/assets/worker-DeESwOs7.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.

v4.7.5

1 finding

LOW No provenance attestation provenance

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

v4.7.4

1 finding

LOW No provenance attestation provenance

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

v4.7.3

1 finding

LOW No provenance attestation provenance

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

v4.7.2

1 finding

LOW No provenance attestation provenance

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

v4.7.1

1 finding

LOW No provenance attestation provenance

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

v4.7.0

1 finding

LOW No provenance attestation provenance

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

v4.6.2

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.

v4.6.1

1 finding

LOW No provenance attestation provenance

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

v4.6.0

2 findings

HIGH New obfuscated file: dist/assets/worker-CDL4vKo-.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.

v4.5.2

2 findings

HIGH New obfuscated file: dist/assets/worker-CDL4vKo-.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.

v4.5.1

2 findings

HIGH New obfuscated file: dist/assets/worker-CDL4vKo-.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.

v4.5.0

2 findings

HIGH New obfuscated file: dist/assets/worker-CDL4vKo-.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.

v4.4.0

1 finding

LOW No provenance attestation provenance

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

v4.3.1

1 finding

LOW No provenance attestation provenance

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

v4.3.0

1 finding

LOW No provenance attestation provenance

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

v4.2.6

1 finding

LOW No provenance attestation provenance

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

v4.2.5

1 finding

LOW No provenance attestation provenance

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

v4.2.4

1 finding

LOW No provenance attestation provenance

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

v4.2.3

1 finding

LOW No provenance attestation provenance

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

v4.2.2

1 finding

LOW No provenance attestation provenance

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

v4.2.1

1 finding

LOW No provenance attestation provenance

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

v4.2.0

1 finding

LOW No provenance attestation provenance

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

v4.1.0

1 finding

LOW No provenance attestation provenance

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

v4.0.3

1 finding

LOW No provenance attestation provenance

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

v4.0.2

1 finding

LOW No provenance attestation provenance

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

v4.0.1

1 finding

LOW No provenance attestation provenance

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

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