string.prototype.startswith
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): Standard es-shim helper deps, common across ljharb-maintained polyfills. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Long-stable takeover pattern across es-shim polyfill packages, not a compromise. | ai |
v1.0.1
2 findingsThis version was published by a different npm account (google-wombot) than the most recent previously approved version (mathias) on 2024-09-27. It has since remained available on npm for 659 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.