fast-printf
Fast and spec-compliant printf implementation for Node.js and browser.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:mathjs | AI (phantom-deps): mathjs is a legitimate package listed as a dependency; used in benchmarks/config. No security concern. | ai | |
| phantom-deps | phantom-dep:boolean | AI (phantom-deps): boolean is a legitimate package listed as a dependency. No security concern. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): postinstall runs 'husky install', a standard dev-tooling pattern for Git hooks setup. It is a no-op when installed as a dependency (no .git dir). Stable false positive for this package. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 1.6.10 | 0 / 12 | |
| 1.6.9 | 1 / 12 | |
| 1.6.8 | 1 / 13 | |
| 1.6.7 | 1 / 13 | |
| 1.6.6 | 1 / 13 | |
| 1.6.5 | 1 / 13 | |
| 1.6.4 | 1 / 13 | |
| 1.6.3 | 2 / 13 | |
| 1.6.2 | 2 / 13 | |
| 1.6.1 | 2 / 13 | |
| 1.6.0 | 2 / 13 | |
| 1.5.11 | 2 / 13 | |
| 1.5.10 | 2 / 13 | |
| 1.5.9 | 2 / 13 | |
| 1.5.8 | 2 / 13 | |
| 1.5.7 | 3 / 13 | |
| 1.5.6 | 2 / 13 | |
| 1.5.5 | 3 / 13 | |
| 1.5.4 | 2 / 13 | |
| 1.5.3 | 2 / 13 | |
| 1.5.2 | 2 / 13 | |
| 1.5.1 | 2 / 13 | |
| 1.5.0 | 3 / 13 | |
| 1.4.1 | 2 / 13 | |
| 1.4.0 | 2 / 13 | |
| 1.3.3 | 2 / 13 | |
| 1.3.2 | 2 / 13 | |
| 1.3.1 | 2 / 13 | |
| 1.3.0 | 2 / 13 | |
| 1.2.0 | 2 / 13 | |
| 1.1.0 | 1 / 13 | |
| 1.0.0 | 1 / 13 |
v1.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
2 findingsScript: husky install
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.