← Home

extsprintf

npm Repository Homepage

extended POSIX-style sprintf

11
Versions
MIT
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

todd.whitemankusorwyattmichael.hicksbahamatchudleytchameroydbuelltrentmdapjclulowarekinathmellockellymclaughlin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change dap→bahamat reflects a legitimate Joyent ecosystem maintainer transition; bahamat has a clean track record and the maintainer list includes well-known Joyent contributors. ai
publish-pattern dormant-publish AI (publish-pattern): Long dormancy followed by a no-material-change publish is consistent with ownership consolidation, not malicious injection. No code changes were introduced. ai

Versions (showing 11 of 11)

Version Deps Published
1.4.1 0 / 0
1.4.0 0 / 0
1.3.0 0 / 0
1.2.1 0 / 0
1.2.0 0 / 0
1.1.1 0 / 0
1.1.0 0 / 0
1.0.3 0 / 0
1.0.2 0 / 0
1.0.1 0 / 0
1.0.0 0 / 0

v1.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.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.

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.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.

v1.0.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.