@motech-development/yarn-plugin-prepare
Run Yarn prepare after every installation
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.3.1 | 0 / 6 | |
| 1.3.0 | 0 / 18 | |
| 1.2.1 | 0 / 18 | |
| 1.2.0 | 0 / 17 | |
| 1.1.0 | 0 / 15 | |
| 1.0.10 | 0 / 14 | |
| 1.0.9 | 0 / 14 | |
| 1.0.8 | 0 / 14 | |
| 1.0.7 | 0 / 14 | |
| 1.0.6 | 0 / 14 | |
| 1.0.5 | 0 / 14 | |
| 1.0.4 | 0 / 14 | |
| 1.0.3 | 0 / 14 | |
| 1.0.2 | 0 / 14 | |
| 1.0.1 | 0 / 13 | |
| 1.0.0 | 0 / 13 |
v1.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.