@stdlib/string-base-format-tokenize Apache-2.0 11 versions

@stdlib/string-base-format-tokenize

npm Repository Homepage

Tokenize a string into an array of string parts and format identifier objects.

11

Versions

Apache-2.0

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

stdlib-botkgryteplaneshifterrreusser

Keywords

stdlibstdstringutilitiesutilityutilsutilstringstrformatformattingfmttokenstokenizetoken

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	url-dep:tape	AI (npm-metadata): Dev-only dependency pinned to maintainer's own fork; no runtime impact.	ai	2026/07/24

Versions (showing 11 of 11)

Version	Deps	Published
0.2.4	0 / 0	2026-02-01
0.2.3	0 / 0	2026-01-25
0.2.2	0 / 0	2024-07-26
0.2.1	0 / 0	2024-02-21
0.2.0	0 / 6	2024-02-14
0.1.1	0 / 5	2023-10-03
0.1.0	0 / 5	2023-09-22
0.0.4	0 / 5	2022-09-17
0.0.3	0 / 5	2022-09-17
0.0.2	0 / 5	2022-07-12
0.0.1	0 / 5	2022-04-04

v0.2.2

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.

v0.2.1

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.

v0.2.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.

v0.1.1

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.

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.

v0.0.4

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.

v0.0.3

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.

v0.0.2

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.

v0.0.1

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.