← Home

string.fromcodepoint

npm Repository Homepage

A robust & optimized `String.fromCodePoint` polyfill, based on the ECMAScript 6 specification.

7
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

mathiasgoogle-wombot

Keywords

stringunicodees6ecmascriptpolyfill

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher changed to google-wombot (Jordan Harband's bot), the canonical es-shims maintainer. Legitimate ecosystem adoption. ai
maintainer-change maintainer-added AI (maintainer-change): google-wombot is Jordan Harband's well-established npm account managing the es-shims ecosystem. ai
maintainer-change maintainer-removed AI (maintainer-change): Original maintainer removal is consistent with legitimate transfer to es-shims ecosystem. ai
publish-pattern new-deps-added AI (publish-pattern): call-bind and get-intrinsic are standard es-shims infrastructure deps, expected for this package pattern. ai

Versions (showing 7 of 7)

Version Deps Published
1.0.3 5 / 9
1.0.2 4 / 9
1.0.1 4 / 9
1.0.0 2 / 5
0.2.1 0 / 0
0.2.0 0 / 0
0.1.0 0 / 0

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

2 findings
HIGH Publisher changed: nicolo-ribaudo → google-wombot (on 2023-05-03) provenance

This version was published by a different npm account than previous versions on 2023-05-03. 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.

v1.0.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: mathias → nicolo-ribaudo (on 2020-05-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-05-21. This could indicate a legitimate maintainer transition or an account compromise.

v0.2.1

1 finding
LOW No provenance attestation provenance

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.