assemblyai
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
Keywords
Versions (showing 76 of 76)
| Version | Deps | Published |
|---|---|---|
| 4.36.3 | 1 / 30 | |
| 4.35.4 | 1 / 30 | |
| 4.35.3 | 1 / 30 | |
| 4.35.0 | 1 / 30 | |
| 4.34.6 | 1 / 30 | |
| 4.34.5 | 1 / 30 | |
| 4.34.4 | 1 / 30 | |
| 4.34.0 | 1 / 30 | |
| 4.33.3 | 1 / 30 | |
| 4.33.2 | 1 / 30 | |
| 4.33.1 | 1 / 30 | |
| 4.33.0 | 1 / 30 | |
| 4.32.1 | 1 / 30 | |
| 4.30.0 | 1 / 30 | |
| 4.29.0 | 1 / 30 | |
| 4.28.0 | 1 / 30 | |
| 4.27.0 | 1 / 30 | |
| 4.26.1 | 1 / 30 | |
| 4.26.0 | 1 / 30 | |
| 4.25.1 | 1 / 30 | |
| 4.25.0 | 1 / 30 | |
| 4.24.0 | 1 / 30 | |
| 4.23.1 | 1 / 30 | |
| 4.23.0 | 1 / 30 | |
| 4.22.1 | 1 / 30 | |
| 4.22.0 | 1 / 30 | |
| 4.21.0 | 1 / 30 | |
| 4.19.0 | 1 / 30 | |
| 4.18.5 | 1 / 30 | |
| 4.18.4 | 1 / 30 | |
| 4.18.2 | 1 / 30 | |
| 4.18.1 | 1 / 30 | |
| 4.18.0 | 1 / 30 | |
| 4.17.0 | 1 / 30 | |
| 4.16.1 | 1 / 30 | |
| 4.16.0 | 1 / 30 | |
| 4.15.0 | 1 / 30 | |
| 4.14.2 | 1 / 30 | |
| 4.14.1 | 1 / 30 | |
| 4.14.0 | 1 / 30 | |
| 4.13.4 | 1 / 30 | |
| 4.13.3 | 1 / 30 | |
| 4.13.2 | 1 / 30 | |
| 4.13.1 | 1 / 30 | |
| 4.13.0 | 1 / 30 | |
| 4.12.2 | 1 / 30 | |
| 4.12.1 | 1 / 30 | |
| 4.12.0 | 1 / 30 | |
| 4.11.0 | 1 / 30 | |
| 4.9.0 | 1 / 30 | |
| 4.8.0 | 1 / 30 | |
| 4.7.1 | 1 / 30 | |
| 4.7.0 | 1 / 30 | |
| 4.6.1 | 1 / 30 | |
| 4.6.0 | 1 / 30 | |
| 4.5.0 | 1 / 31 | |
| 4.4.7 | 1 / 31 | |
| 4.4.6 | 1 / 31 | |
| 4.4.5 | 1 / 31 | |
| 4.4.4 | 1 / 31 | |
| 4.4.3 | 1 / 29 | |
| 4.4.2 | 1 / 29 | |
| 4.4.1 | 1 / 29 | |
| 4.4.0 | 1 / 29 | |
| 4.3.4 | 1 / 28 | |
| 4.3.3 | 1 / 28 | |
| 4.3.2 | 1 / 28 | |
| 4.3.1 | 1 / 27 | |
| 4.3.0 | 1 / 27 | |
| 4.2.3 | 1 / 27 | |
| 4.2.2 | 1 / 27 | |
| 4.2.1 | 1 / 27 | |
| 4.2.0 | 1 / 27 | |
| 4.1.0 | 1 / 27 | |
| 4.0.1 | 1 / 27 | |
| 4.0.0 | 1 / 27 |
v4.36.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.35.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.35.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.