@wildix/wda-stream-client
@wildix/wda-stream-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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist-cjs/schemas/schemas_0.js | AI (source-diff): Smithy SDK codegen output with long export lines; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist-es/schemas/schemas_0.js | AI (source-diff): Smithy SDK codegen pattern using short string-constant aliases; not obfuscation. | ai | |
| phantom-deps | phantom-dep:@smithy/middleware-stack | AI (phantom-deps): Smithy framework-scoped package; loaded by convention in AWS SDK clients. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-logger | AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in AWS client libraries. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/types | AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in AWS client libraries. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-host-header | AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in AWS client libraries. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-recursion-detection | AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in AWS client libraries. | ai | |
| phantom-deps | phantom-dep:@smithy/invalid-dependency | AI (phantom-deps): Smithy framework-scoped package; loaded by convention in AWS SDK clients. | ai | |
| phantom-deps | phantom-dep:@smithy/config-resolver | AI (phantom-deps): Smithy framework-scoped package; loaded by convention in AWS SDK clients. | ai |
Versions (showing 20 of 120)
| Version | Deps | Published |
|---|---|---|
| 1.0.21 | 30 / 6 | |
| 1.0.20 | 30 / 6 | |
| 1.0.19 | 30 / 6 | |
| 1.0.18 | 30 / 7 | |
| 1.0.17 | 30 / 7 | |
| 1.0.16 | 26 / 8 | |
| 1.0.14 | 26 / 8 | |
| 1.0.13 | 26 / 8 | |
| 1.0.12 | 26 / 8 | |
| 1.0.11 | 26 / 8 | |
| 1.0.10 | 26 / 8 | |
| 1.0.9 | 26 / 8 | |
| 1.0.8 | 26 / 8 | |
| 1.0.7 | 26 / 8 | |
| 1.0.6 | 26 / 8 | |
| 1.0.5 | 26 / 8 | |
| 1.0.4 | 26 / 8 | |
| 1.0.3 | 26 / 8 | |
| 1.0.2 | 26 / 8 | |
| 1.0.1 | 26 / 8 |
v1.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.