@wildix/wim-knowledge-base-client
@wildix/wim-knowledge-base-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 convention-loaded dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@smithy/config-resolver | AI (phantom-deps): AWS SDK convention-loaded dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@smithy/middleware-stack | AI (phantom-deps): AWS SDK convention-loaded dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-logger | AI (phantom-deps): AWS SDK convention-loaded dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@smithy/invalid-dependency | AI (phantom-deps): AWS SDK convention-loaded dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-host-header | AI (phantom-deps): AWS SDK convention-loaded dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-recursion-detection | AI (phantom-deps): AWS SDK convention-loaded dependency; stable for this package. | ai |
Versions (showing 51 of 64)
| Version | Deps | Published |
|---|---|---|
| 0.1.8 | 34 / 6 | |
| 0.1.7 | 34 / 6 | |
| 0.1.6 | 34 / 6 | |
| 0.1.5 | 34 / 6 | |
| 0.1.4 | 34 / 6 | |
| 0.1.3 | 34 / 6 | |
| 0.1.2 | 34 / 6 | |
| 0.1.1 | 34 / 6 | |
| 0.1.0 | 34 / 6 | |
| 0.0.66 | 34 / 6 | |
| 0.0.65 | 34 / 6 | |
| 0.0.64 | 34 / 6 | |
| 0.0.62 | 34 / 6 | |
| 0.0.61 | 34 / 6 | |
| 0.0.60 | 34 / 6 | |
| 0.0.59 | 34 / 6 | |
| 0.0.56 | 34 / 6 | |
| 0.0.55 | 34 / 6 | |
| 0.0.54 | 34 / 6 | |
| 0.0.53 | 34 / 6 | |
| 0.0.52 | 34 / 6 | |
| 0.0.51 | 34 / 6 | |
| 0.0.50 | 34 / 6 | |
| 0.0.49 | 34 / 6 | |
| 0.0.48 | 34 / 6 | |
| 0.0.47 | 34 / 6 | |
| 0.0.46 | 34 / 6 | |
| 0.0.45 | 34 / 6 | |
| 0.0.44 | 34 / 6 | |
| 0.0.43 | 34 / 6 | |
| 0.0.42 | 34 / 6 | |
| 0.0.41 | 34 / 6 | |
| 0.0.40 | 34 / 6 | |
| 0.0.39 | 34 / 6 | |
| 0.0.38 | 34 / 6 | |
| 0.0.37 | 34 / 6 | |
| 0.0.36 | 34 / 6 | |
| 0.0.35 | 34 / 6 | |
| 0.0.34 | 34 / 6 | |
| 0.0.33 | 34 / 6 | |
| 0.0.32 | 34 / 6 | |
| 0.0.31 | 34 / 6 | |
| 0.0.30 | 34 / 6 | |
| 0.0.29 | 34 / 6 | |
| 0.0.28 | 34 / 6 | |
| 0.0.27 | 34 / 6 | |
| 0.0.26 | 34 / 6 | |
| 0.0.25 | 34 / 6 | |
| 0.0.24 | 34 / 6 | |
| 0.0.23 | 34 / 6 | |
| 0.0.22 | 34 / 6 |
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.