@polkadot/x-textdecoder Apache-2.0 23 versions

@polkadot/x-textdecoder

npm Repository Homepage

A TextDecoder replacement

23

Versions

Apache-2.0

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

jacogrpolkadotjsparitytech-ci

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-added	AI (maintainer-change): paritytech-ci is Parity Technologies' CI account with 607 approved packages and 0 rejections — a legitimate organizational publisher for the polkadot-js ecosystem.	ai	2026/04/23
provenance	publisher-changed	AI (provenance): Transition from polkadotjs to paritytech-ci reflects a legitimate org-level CI publishing consolidation; paritytech-ci has a clean track record across 607 approved packages.	ai	2026/04/23

Versions (showing 23 of 23)

Version	Deps	Published
14.0.3	2 / 0	2026-03-23
14.0.2	2 / 0	2026-03-16
14.0.1	2 / 0	2025-12-09
13.5.9	2 / 0	2025-11-25
13.5.8	2 / 0	2025-11-11
13.5.7	2 / 0	2025-10-13
13.5.6	2 / 0	2025-08-26
13.5.5	2 / 0	2025-08-11
13.5.4	2 / 0	2025-07-28
13.5.3	2 / 0	2025-07-01
13.5.2	2 / 0	2025-06-17
13.5.1	2 / 0	2025-05-19
13.4.4	2 / 0	2025-04-14
13.4.3	2 / 0	2025-02-17
13.4.2	2 / 0	2025-02-17
13.4.1	2 / 0	2025-02-17
13.3.1	2 / 0	2025-01-06
13.2.3	2 / 0	2024-11-11
13.2.2	2 / 0	2024-10-28
13.2.1	2 / 0	2024-10-21
13.1.1	2 / 0	2024-09-16
13.0.2	2 / 0	2024-07-13
13.0.1	2 / 0	2024-07-12

v14.0.2

2 findings

HIGH Publisher changed: polkadotjs → paritytech-ci (on 2026-03-16) provenance

This version was published by a different npm account than previous versions on 2026-03-16. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v14.0.1

1 finding

LOW No provenance attestation provenance

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

v13.5.9

1 finding

LOW No provenance attestation provenance

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

v13.5.8

1 finding

LOW No provenance attestation provenance

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

v13.5.7

1 finding

LOW No provenance attestation provenance

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

v13.5.6

1 finding

LOW No provenance attestation provenance

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

v13.5.5

1 finding

LOW No provenance attestation provenance

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

v13.5.4

1 finding

LOW No provenance attestation provenance

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

v13.5.3

1 finding

LOW No provenance attestation provenance

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

v13.5.2

1 finding

LOW No provenance attestation provenance

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

v13.5.1

1 finding

LOW No provenance attestation provenance

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

v13.4.4

1 finding

LOW No provenance attestation provenance

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

v13.4.3

1 finding

LOW No provenance attestation provenance

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

v13.4.2

1 finding

LOW No provenance attestation provenance

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

v13.4.1

1 finding

LOW No provenance attestation provenance

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

v13.3.1

1 finding

LOW No provenance attestation provenance

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

v13.2.3

1 finding

LOW No provenance attestation provenance

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

v13.2.2

1 finding

LOW No provenance attestation provenance

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

v13.2.1

1 finding

LOW No provenance attestation provenance

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

v13.1.1

1 finding

LOW No provenance attestation provenance

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

v13.0.2

1 finding

LOW No provenance attestation provenance

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

v13.0.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.