@stdlib/string-format
Insert supplied variable values into a format string.
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:@stdlib/string-lowercase | AI (dependencies): Official stdlib sibling package, same monorepo/publisher. | ai | |
| dependencies | unvetted-dep:@stdlib/string-uppercase | AI (dependencies): Official stdlib sibling package, same monorepo/publisher. | ai | |
| dependencies | unvetted-dep:@stdlib/string-starts-with | AI (dependencies): Official stdlib sibling package, same monorepo/publisher. | ai | |
| dependencies | unvetted-dep:@stdlib/assert-is-uppercase | AI (dependencies): Official stdlib sibling package, same monorepo/publisher. | ai | |
| npm-metadata | url-dep:tape | AI (npm-metadata): Dev-only test dependency pinned to known contributor fork, no runtime impact. | ai | |
| provenance | no-provenance | AI (provenance): stdlib packages consistently lack provenance attestation; stable false positive for this publisher. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.2.3 | 2 / 0 | |
| 0.2.2 | 2 / 0 | |
| 0.2.1 | 2 / 0 | |
| 0.2.0 | 2 / 9 | |
| 0.1.1 | 2 / 8 | |
| 0.1.0 | 2 / 8 | |
| 0.0.3 | 2 / 8 | |
| 0.0.2 | 2 / 8 | |
| 0.0.1 | 12 / 7 |
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.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.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.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.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.