@projectstorm/react-workspaces-dropzone-plugin-tabs
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.3.2 | 6 / 1 | |
| 2.3.1 | 6 / 1 | |
| 2.3.0 | 6 / 1 | |
| 2.2.15 | 6 / 1 | |
| 2.2.14 | 6 / 1 | |
| 2.2.13 | 6 / 1 | |
| 2.2.12 | 6 / 1 | |
| 2.2.11 | 6 / 1 | |
| 2.2.10 | 6 / 1 | |
| 2.2.9 | 6 / 1 | |
| 2.2.8 | 6 / 1 |
v2.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.