← Home

@cto.af/textdecoder

npm Repository Homepage

Quick wrapper that finds TextDecoder in your runtime, or uses an adequate polyfill

8
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

hildjj

Keywords

TextDecoderutf8utf-8polyfill

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Package is 5+ years old with 8 versions and a highly trusted publisher. Version 0.0.0 is a deliberate versioning choice, not a malware indicator. ai
provenance publisher-changed AI (provenance): Publisher changed from hildjj to GitHub Actions as part of a legitimate CI/CD migration; SLSA provenance attestation confirms the artifact originates from the hildjj/ctoaf-textdecoder repo. ai

Versions (showing 8 of 8)

Version Deps Published
0.3.0 0 / 0
0.2.4 0 / 0
0.2.2 0 / 0
0.2.1 0 / 0
0.2.0 0 / 5
0.1.0 0 / 5
0.0.1 0 / 5
0.0.0 0 / 4

v0.3.0

2 findings
HIGH Publisher changed: hildjj → GitHub Actions (on 2026-03-03) provenance

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

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

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

1 finding
LOW No provenance attestation provenance

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

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