pff
Minimal implementation of printf, which is really fast
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Package is 4327 days old with 6 versions; 0.0.0 is simply the initial release of a legitimate long-standing utility, not a throwaway malicious package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): pff stands for 'PrintF Ftw' — a string formatting utility with no relation to the PostgreSQL client 'pg'. Levenshtein proximity is coincidental. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 0 / 2 | |
| 0.2.0 | 0 / 10 | |
| 0.1.1 | 0 / 9 | |
| 0.1.0 | 0 / 9 | |
| 0.0.1 | 0 / 10 | |
| 0.0.0 | 0 / 7 |
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.