@wildix/auth-api-keys-client
@wildix/auth-api-keys-client client
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:@aws-sdk/types | AI (phantom-deps): AWS SDK framework convention; declared in dependencies. | ai | |
| phantom-deps | phantom-dep:@smithy/config-resolver | AI (phantom-deps): AWS SDK framework convention; declared in dependencies. | ai | |
| phantom-deps | phantom-dep:@smithy/middleware-stack | AI (phantom-deps): AWS SDK framework convention; declared in dependencies. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-logger | AI (phantom-deps): AWS SDK framework convention; declared in dependencies. | ai | |
| phantom-deps | phantom-dep:@smithy/invalid-dependency | AI (phantom-deps): AWS SDK framework convention; declared in dependencies. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-host-header | AI (phantom-deps): AWS SDK framework convention; declared in dependencies. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-recursion-detection | AI (phantom-deps): AWS SDK framework convention; declared in dependencies. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.1.0 | 34 / 6 | |
| 0.0.18 | 34 / 6 | |
| 0.0.17 | 34 / 6 | |
| 0.0.15 | 34 / 6 | |
| 0.0.14 | 34 / 6 | |
| 0.0.12 | 34 / 6 | |
| 0.0.11 | 34 / 6 | |
| 0.0.10 | 34 / 6 | |
| 0.0.9 | 34 / 6 |
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.