@things-factory/screencast-proxy-service
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 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 4.3.815 | 3 / 0 | |
| 4.3.767 | 3 / 0 | |
| 4.3.764 | 3 / 0 | |
| 4.3.755 | 3 / 0 | |
| 4.3.752 | 3 / 0 | |
| 4.3.743 | 3 / 0 | |
| 4.3.740 | 3 / 0 | |
| 4.3.738 | 3 / 0 | |
| 4.3.734 | 3 / 0 | |
| 4.3.729 | 3 / 0 | |
| 4.3.727 | 3 / 0 | |
| 4.3.725 | 3 / 0 | |
| 4.3.723 | 3 / 0 | |
| 4.3.705 | 3 / 0 | |
| 4.3.695 | 3 / 0 | |
| 4.3.689 | 3 / 0 | |
| 4.3.675 | 3 / 0 | |
| 4.3.673 | 3 / 0 | |
| 4.3.672 | 3 / 0 | |
| 4.3.671 | 3 / 0 | |
| 4.3.591 | 3 / 0 | |
| 4.3.535 | 3 / 0 | |
| 4.3.534 | 3 / 0 | |
| 4.3.533 | 3 / 0 | |
| 4.3.526 | 3 / 0 |
v4.3.591
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.535
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.534
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.533
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.526
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.