mux-embed
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
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 5.18.1 | 0 / 14 | |
| 5.18.0 | 0 / 13 | |
| 5.17.6 | 0 / 13 | |
| 5.17.4 | 0 / 13 | |
| 5.17.3 | 0 / 13 | |
| 5.16.1 | 0 / 13 | |
| 5.16.0 | 0 / 13 | |
| 5.15.0 | 0 / 13 | |
| 5.14.0 | 0 / 13 | |
| 5.13.0 | 0 / 13 | |
| 5.12.0 | 0 / 13 | |
| 5.11.0 | 0 / 13 | |
| 5.10.0 | 0 / 13 | |
| 5.9.0 | 0 / 13 | |
| 5.8.3 | 0 / 13 | |
| 5.8.2 | 0 / 13 | |
| 5.8.1 | 0 / 13 | |
| 5.8.0 | 0 / 13 | |
| 5.7.0 | 0 / 13 | |
| 5.6.0 | 0 / 13 | |
| 5.5.0 | 0 / 13 | |
| 5.4.3 | 0 / 13 | |
| 5.4.2 | 0 / 13 | |
| 5.4.1 | 0 / 13 | |
| 5.4.0 | 0 / 13 | |
| 5.3.3 | 0 / 13 | |
| 5.3.2 | 0 / 13 | |
| 5.3.1 | 0 / 13 | |
| 5.3.0 | 0 / 16 | |
| 5.2.1 | 0 / 16 | |
| 5.2.0 | 0 / 16 | |
| 5.1.0 | 0 / 16 | |
| 5.0.0 | 0 / 12 |
v5.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.