string.prototype.matchall
Spec-compliant polyfill for String.prototype.matchAll
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:gopd | AI (dependencies): gopd is a standard es-shims ecosystem package maintained by ljharb; its use here is expected and legitimate. | ai | |
| dependencies | unvetted-dep:define-properties | AI (dependencies): define-properties is a core es-shims utility maintained by ljharb; standard dependency for this polyfill package. | ai | |
| dependencies | unvetted-dep:set-function-name | AI (dependencies): set-function-name is a standard es-shims utility maintained by ljharb; expected dependency for this polyfill. | ai | |
| phantom-deps | phantom-dep:side-channel | AI (phantom-deps): side-channel is a declared runtime dep in package.json used within the es-shims ecosystem; phantom signal is a false positive here. | ai | |
| phantom-deps | phantom-dep:internal-slot | AI (phantom-deps): internal-slot is a declared runtime dep in package.json used within the es-shims ecosystem; phantom signal is a false positive here. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 4.0.12 | 13 / 19 | |
| 4.0.11 | 12 / 19 | |
| 4.0.10 | 9 / 19 | |
| 4.0.9 | 8 / 19 | |
| 4.0.8 | 8 / 19 | |
| 4.0.7 | 8 / 16 | |
| 4.0.6 | 8 / 16 | |
| 4.0.5 | 8 / 15 | |
| 4.0.4 | 7 / 15 | |
| 4.0.3 | 7 / 15 | |
| 4.0.2 | 6 / 14 | |
| 4.0.1 | 4 / 14 | |
| 4.0.0 | 5 / 12 |
v4.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.