monosize
<div align="center"> <img width="600" alt="A sample report produced by monosize" src="https://raw.githubusercontent.com/microsoft/monosize/main/.github/images/gh-report.png"> <h1>monosize 📦</h1> <b>Mono</b>repo + bundle<b>size</b> <br/> <span>M
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 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 8 / 0 | |
| 0.9.0 | 8 / 0 | |
| 0.8.3 | 8 / 0 | |
| 0.8.2 | 8 / 0 | |
| 0.8.1 | 8 / 0 | |
| 0.8.0 | 10 / 0 | |
| 0.7.1 | 10 / 0 | |
| 0.7.0 | 10 / 0 | |
| 0.6.3 | 10 / 0 | |
| 0.6.2 | 10 / 0 | |
| 0.6.1 | 11 / 0 | |
| 0.6.0 | 11 / 0 | |
| 0.5.1 | 11 / 0 | |
| 0.5.0 | 11 / 0 | |
| 0.4.0 | 11 / 0 | |
| 0.3.0 | 16 / 0 | |
| 0.2.2 | 16 / 0 |
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.