@aws-sdk/middleware-sdk-transcribe-streaming
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Runtime implicit dependency; stable for AWS SDK packages. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/types | AI (phantom-deps): Framework-scoped AWS package loaded by convention; stable pattern. | ai | |
| phantom-deps | phantom-dep:@smithy/signature-v4 | AI (phantom-deps): Framework-scoped Smithy package loaded by convention; stable pattern. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/util-format-url | AI (phantom-deps): Framework-scoped AWS package loaded by convention; stable pattern. | ai | |
| phantom-deps | phantom-dep:@smithy/eventstream-serde-browser | AI (phantom-deps): Framework-scoped Smithy package loaded by convention; stable pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; minimal README/keywords expected. | ai |
Versions (showing 100 of 228)
| Version | Deps | Published |
|---|---|---|
| 3.972.28 | 4 / 6 | |
| 3.972.27 | 4 / 6 | |
| 3.972.26 | 4 / 6 | |
| 3.972.25 | 4 / 6 | |
| 3.972.24 | 4 / 6 | |
| 3.972.23 | 4 / 6 | |
| 3.972.22 | 4 / 6 | |
| 3.972.21 | 4 / 6 | |
| 3.972.20 | 4 / 6 | |
| 3.972.19 | 4 / 6 | |
| 3.972.18 | 4 / 6 | |
| 3.972.17 | 4 / 6 | |
| 3.972.16 | 4 / 6 | |
| 3.972.15 | 6 / 6 | |
| 3.972.14 | 6 / 6 | |
| 3.972.13 | 6 / 6 | |
| 3.972.12 | 6 / 6 | |
| 3.972.11 | 6 / 6 | |
| 3.972.10 | 8 / 6 | |
| 3.972.9 | 8 / 6 | |
| 3.972.8 | 8 / 6 | |
| 3.972.7 | 8 / 6 | |
| 3.972.6 | 8 / 6 | |
| 3.972.5 | 8 / 6 | |
| 3.972.4 | 8 / 6 | |
| 3.972.3 | 8 / 6 | |
| 3.972.2 | 8 / 6 | |
| 3.972.1 | 8 / 6 | |
| 3.972.0 | 8 / 6 | |
| 3.969.0 | 8 / 6 | |
| 3.968.0 | 8 / 6 | |
| 3.965.0 | 8 / 6 | |
| 3.957.0 | 8 / 6 | |
| 3.956.0 | 8 / 6 | |
| 3.953.0 | 8 / 6 | |
| 3.936.0 | 8 / 6 | |
| 3.930.0 | 8 / 6 | |
| 3.922.0 | 8 / 6 | |
| 3.921.0 | 8 / 6 | |
| 3.920.0 | 8 / 6 | |
| 3.914.0 | 8 / 6 | |
| 3.910.0 | 8 / 6 | |
| 3.901.0 | 8 / 6 | |
| 3.896.0 | 8 / 6 | |
| 3.893.0 | 8 / 6 | |
| 3.891.0 | 8 / 6 | |
| 3.890.0 | 8 / 6 | |
| 3.887.0 | 8 / 6 | |
| 3.873.0 | 8 / 6 | |
| 3.862.0 | 8 / 6 | |
| 3.840.0 | 8 / 6 | |
| 3.821.0 | 8 / 6 | |
| 3.804.0 | 8 / 6 | |
| 3.796.0 | 8 / 6 | |
| 3.775.0 | 8 / 6 | |
| 3.734.0 | 8 / 6 | |
| 3.731.0 | 8 / 6 | |
| 3.723.0 | 8 / 6 | |
| 3.714.0 | 8 / 6 | |
| 3.713.0 | 8 / 6 | |
| 3.709.0 | 8 / 6 | |
| 3.696.0 | 8 / 6 | |
| 3.693.0 | 8 / 6 | |
| 3.692.0 | 8 / 6 | |
| 3.691.0 | 8 / 6 | |
| 3.686.0 | 8 / 6 | |
| 3.679.0 | 8 / 6 | |
| 3.674.0 | 8 / 7 | |
| 3.667.0 | 8 / 8 | |
| 3.664.0 | 8 / 8 | |
| 3.662.0 | 8 / 8 | |
| 3.658.1 | 8 / 8 | |
| 3.654.0 | 8 / 8 | |
| 3.649.0 | 8 / 8 | |
| 3.629.0 | 8 / 8 | |
| 3.620.0 | 8 / 8 | |
| 3.616.0 | 8 / 8 | |
| 3.613.0 | 8 / 8 | |
| 3.609.0 | 8 / 8 | |
| 3.598.0 | 8 / 8 | |
| 3.577.0 | 8 / 8 | |
| 3.575.0 | 8 / 8 | |
| 3.569.0 | 8 / 8 | |
| 3.567.0 | 8 / 8 | |
| 3.556.0 | 8 / 8 | |
| 3.552.0 | 8 / 8 | |
| 3.535.0 | 8 / 8 | |
| 3.533.0 | 8 / 8 | |
| 3.523.0 | 8 / 8 | |
| 3.521.0 | 8 / 8 | |
| 3.515.0 | 8 / 8 | |
| 3.511.0 | 8 / 8 | |
| 3.502.0 | 8 / 8 | |
| 3.496.0 | 8 / 8 | |
| 3.495.0 | 8 / 8 | |
| 3.489.0 | 8 / 8 | |
| 3.485.0 | 8 / 8 | |
| 3.468.0 | 8 / 8 | |
| 3.465.0 | 8 / 8 | |
| 3.460.0 | 8 / 9 |
v3.972.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.972.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.972.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.972.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.972.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.972.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.972.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.796.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.775.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.734.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.731.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.723.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.714.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.713.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.709.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.696.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.693.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.692.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.691.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.686.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.679.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.674.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.667.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.664.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.662.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.658.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.654.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.649.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.629.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.620.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.616.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.613.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.609.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.598.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.577.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.575.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.569.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.567.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.556.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.552.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.535.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.533.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.523.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.521.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.515.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.511.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.502.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.496.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.495.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.489.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.485.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.468.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.465.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.460.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.