@cspell/cspell-bundled-dicts
Dictionaries bundled with cspell
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 51 of 190)
| Version | Deps | Published |
|---|---|---|
| 10.0.0 | 59 / 3 | |
| 9.8.0 | 59 / 3 | |
| 9.6.2 | 59 / 2 | |
| 9.3.1 | 58 / 2 | |
| 9.2.1 | 58 / 2 | |
| 9.2.0 | 58 / 2 | |
| 9.1.3 | 58 / 2 | |
| 9.0.2 | 58 / 2 | |
| 9.0.1 | 58 / 2 | |
| 8.19.4 | 58 / 2 | |
| 8.19.3 | 58 / 2 | |
| 8.19.1 | 58 / 2 | |
| 8.17.3 | 58 / 2 | |
| 8.14.4 | 53 / 2 | |
| 8.14.1 | 52 / 2 | |
| 8.8.2 | 51 / 2 | |
| 8.7.0 | 51 / 2 | |
| 8.6.1 | 50 / 2 | |
| 8.6.0 | 48 / 2 | |
| 8.5.0 | 48 / 2 | |
| 8.4.1 | 48 / 2 | |
| 8.4.0 | 48 / 2 | |
| 8.3.2 | 48 / 2 | |
| 8.3.1 | 48 / 2 | |
| 8.3.0 | 48 / 2 | |
| 8.2.4 | 48 / 2 | |
| 8.2.3 | 48 / 2 | |
| 8.2.1 | 48 / 2 | |
| 8.2.0 | 48 / 2 | |
| 8.1.3 | 48 / 2 | |
| 8.1.2 | 48 / 2 | |
| 8.1.1 | 48 / 2 | |
| 8.1.0 | 48 / 2 | |
| 8.0.0 | 48 / 2 | |
| 7.3.9 | 48 / 2 | |
| 7.3.8 | 47 / 2 | |
| 7.3.7 | 47 / 2 | |
| 7.3.6 | 47 / 2 | |
| 7.3.5 | 47 / 2 | |
| 7.3.4 | 47 / 2 | |
| 7.3.3 | 47 / 2 | |
| 7.3.2 | 47 / 2 | |
| 7.3.1 | 47 / 2 | |
| 7.3.0 | 47 / 2 | |
| 7.2.0 | 47 / 2 | |
| 7.1.1 | 47 / 2 | |
| 7.0.2 | 47 / 2 | |
| 7.0.1 | 47 / 2 | |
| 7.0.0 | 47 / 2 | |
| 6.31.3 | 46 / 3 | |
| 6.31.2 | 46 / 3 |
v10.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.19.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.19.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.19.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.17.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.