@defra/flood-webchat
## Useful Links - [Development Guide](./docs/development-guide.md) - [How to Publish](./docs/how-to-publish.md)
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.0.24 | 9 / 27 | |
| 1.0.23 | 9 / 27 | |
| 1.0.22 | 9 / 27 | |
| 1.0.21 | 9 / 27 | |
| 1.0.20 | 9 / 27 | |
| 1.0.19 | 9 / 27 | |
| 1.0.12 | 10 / 28 |
v1.0.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.