@credenza3/passport-sui
Credenza Passport
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@credenza3/scanner-lib | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@credenza3/core-web-sui-ext | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@credenza3/core-web-sui-zklogin-ext | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lean-qr | AI (phantom-deps): Referenced in config/build files; bundled output pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:lodash.merge | AI (phantom-deps): Referenced in config files; bundled output pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:@zerodevx/svelte-toast | AI (phantom-deps): Referenced in config files; bundled output pattern, stable false positive. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.3.29 | 9 / 28 | |
| 0.3.28 | 9 / 28 | |
| 0.3.26 | 9 / 28 | |
| 0.3.25 | 9 / 28 | |
| 0.3.24 | 9 / 28 | |
| 0.3.23 | 9 / 28 | |
| 0.3.22 | 9 / 28 | |
| 0.3.21 | 9 / 28 |
v0.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.