@plasmicapp/loader-splits
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 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.0.74 | 1 / 2 | |
| 1.0.73 | 1 / 2 | |
| 1.0.72 | 1 / 2 | |
| 1.0.71 | 1 / 2 | |
| 1.0.70 | 1 / 2 | |
| 1.0.69 | 1 / 2 | |
| 1.0.68 | 1 / 2 | |
| 1.0.67 | 1 / 2 | |
| 1.0.66 | 1 / 2 | |
| 1.0.65 | 1 / 2 | |
| 1.0.64 | 1 / 2 | |
| 1.0.63 | 1 / 2 | |
| 1.0.62 | 1 / 2 | |
| 1.0.61 | 1 / 2 |
v1.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.