string.prototype.padend
ES2017 spec-compliant String.prototype.padEnd shim.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:define-properties | AI (dependencies): define-properties is a core es-shims utility maintained by the same author (ljharb); its use is standard across all es-shim packages and poses no risk. | ai | |
| provenance | no-provenance | AI (provenance): ljharb's shim packages consistently lack Sigstore provenance; this is a known pattern for this publisher and not a risk indicator. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 3.1.6 | 4 / 12 | |
| 3.1.5 | 3 / 13 | |
| 3.1.4 | 3 / 13 | |
| 3.1.3 | 3 / 10 | |
| 3.1.2 | 3 / 10 | |
| 3.1.1 | 3 / 10 | |
| 3.1.0 | 2 / 7 | |
| 3.0.0 | 3 / 7 |
v3.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.