@pgpm/totp
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @pgpm package; Levenshtein match to 'got' is coincidental, no impersonation intent. | ai | |
| phantom-deps | phantom-dep:@pgpm/base32 | AI (phantom-deps): Same-org dependency; likely used indirectly via pgpm bundling rather than direct import. | ai | |
| phantom-deps | phantom-dep:@pgpm/verify | AI (phantom-deps): Same-org dependency; likely used indirectly via pgpm bundling rather than direct import. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 0.33.0 | 2 / 1 | |
| 0.32.0 | 2 / 1 | |
| 0.31.0 | 2 / 1 | |
| 0.30.0 | 2 / 1 | |
| 0.29.0 | 2 / 1 | |
| 0.28.4 | 2 / 1 | |
| 0.28.3 | 2 / 1 | |
| 0.28.0 | 2 / 1 | |
| 0.27.0 | 2 / 1 | |
| 0.26.6 | 2 / 1 | |
| 0.26.0 | 2 / 1 | |
| 0.23.0 | 2 / 1 | |
| 0.22.0 | 2 / 1 | |
| 0.21.2 | 2 / 1 | |
| 0.21.0 | 2 / 1 | |
| 0.20.0 | 2 / 1 | |
| 0.19.1 | 2 / 1 | |
| 0.19.0 | 2 / 1 | |
| 0.18.0 | 2 / 1 | |
| 0.17.0 | 2 / 1 | |
| 0.16.0 | 2 / 1 | |
| 0.15.5 | 2 / 1 | |
| 0.15.4 | 2 / 1 | |
| 0.15.3 | 2 / 1 | |
| 0.15.2 | 2 / 1 | |
| 0.15.1 | 2 / 1 | |
| 0.15.0 | 2 / 1 | |
| 0.14.0 | 2 / 1 | |
| 0.13.0 | 2 / 1 | |
| 0.12.0 | 2 / 1 | |
| 0.11.1 | 2 / 1 | |
| 0.11.0 | 2 / 1 | |
| 0.10.0 | 2 / 1 | |
| 0.9.0 | 2 / 1 | |
| 0.8.0 | 2 / 1 | |
| 0.7.2 | 2 / 1 | |
| 0.7.1 | 2 / 1 | |
| 0.7.0 | 2 / 1 | |
| 0.6.0 | 2 / 1 | |
| 0.5.0 | 2 / 1 | |
| 0.4.0 | 2 / 1 |
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pyramation) than the most recent previously approved version (zetazz) on 2026-07-09, but pyramation is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.28.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (zetazz) than the most recent previously approved version (pyramation) on 2026-07-01, but zetazz is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.