cspell
A Spelling Checker for Code!
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are first-party @cspell/ scoped packages at the same version, from the same monorepo. Not an external supply chain risk. | ai | |
| dependencies | unvetted-dep:fast-json-stable-stringify | AI (dependencies): fast-json-stable-stringify is a well-known, widely-used utility with no security issues; its use in cspell is stable and expected across versions. | ai | |
| source-diff | obfuscated-file:dist/esm/app.js | AI (source-diff): Bundled output from tsdown build tool; code is readable with meaningful names, not obfuscated. Standard for this package's build pipeline. | ai | |
| phantom-deps | phantom-dep:@cspell/cspell-worker | AI (phantom-deps): First-party monorepo package used as a runtime worker; phantom detection is a false positive for bundled CLI packages. | ai | |
| phantom-deps | phantom-dep:fast-json-stable-stringify | AI (phantom-deps): Well-known utility; phantom detection is a false positive for bundled output where imports are resolved at build time. | ai | |
| phantom-deps | phantom-dep:@cspell/cspell-json-reporter | AI (phantom-deps): First-party monorepo reporter package; phantom detection is a false positive for bundled CLI packages with dynamic plugin loading. | ai |
Versions (showing 100 of 409)
| Version | Deps | Published |
|---|---|---|
| 10.0.0 | 21 / 4 | |
| 9.8.0 | 21 / 4 | |
| 9.7.0 | 21 / 4 | |
| 9.6.4 | 21 / 4 | |
| 9.6.3 | 21 / 4 | |
| 9.6.2 | 21 / 4 | |
| 9.6.1 | 21 / 4 | |
| 9.6.0 | 19 / 4 | |
| 9.4.0 | 19 / 5 | |
| 9.3.2 | 18 / 5 | |
| 9.3.1 | 18 / 5 | |
| 9.3.0 | 18 / 5 | |
| 9.2.2 | 18 / 5 | |
| 9.2.1 | 18 / 5 | |
| 9.2.0 | 18 / 5 | |
| 9.1.5 | 18 / 6 | |
| 9.1.3 | 18 / 6 | |
| 9.1.2 | 18 / 6 | |
| 9.1.1 | 18 / 6 | |
| 9.1.0 | 18 / 6 | |
| 9.0.2 | 17 / 6 | |
| 9.0.1 | 17 / 6 | |
| 9.0.0 | 17 / 6 | |
| 8.19.4 | 17 / 6 | |
| 8.19.3 | 17 / 6 | |
| 8.19.2 | 18 / 6 | |
| 8.19.1 | 18 / 6 | |
| 8.19.0 | 18 / 6 | |
| 8.18.1 | 18 / 6 | |
| 8.18.0 | 18 / 6 | |
| 8.17.5 | 18 / 6 | |
| 8.17.4 | 18 / 6 | |
| 8.17.3 | 18 / 6 | |
| 8.17.2 | 18 / 6 | |
| 8.17.1 | 18 / 6 | |
| 8.17.0 | 18 / 6 | |
| 8.16.1 | 18 / 6 | |
| 8.16.0 | 18 / 6 | |
| 8.15.7 | 18 / 6 | |
| 8.15.6 | 18 / 6 | |
| 8.15.5 | 18 / 6 | |
| 8.15.4 | 18 / 6 | |
| 8.15.3 | 18 / 6 | |
| 8.15.2 | 18 / 6 | |
| 8.15.1 | 18 / 6 | |
| 8.15.0 | 18 / 6 | |
| 8.14.4 | 19 / 6 | |
| 8.14.3 | 19 / 6 | |
| 8.14.2 | 19 / 6 | |
| 8.14.1 | 19 / 6 | |
| 8.13.3 | 19 / 6 | |
| 8.13.2 | 19 / 6 | |
| 8.13.1 | 19 / 6 | |
| 8.13.0 | 19 / 6 | |
| 8.12.1 | 18 / 6 | |
| 8.11.0 | 18 / 6 | |
| 8.10.4 | 18 / 6 | |
| 8.10.2 | 18 / 6 | |
| 8.10.1 | 18 / 6 | |
| 8.10.0 | 18 / 6 | |
| 8.9.1 | 18 / 6 | |
| 8.9.0 | 18 / 6 | |
| 8.8.4 | 18 / 6 | |
| 8.8.3 | 18 / 6 | |
| 8.8.2 | 18 / 6 | |
| 8.8.1 | 18 / 6 | |
| 8.8.0 | 18 / 6 | |
| 8.7.0 | 18 / 6 | |
| 8.6.1 | 18 / 6 | |
| 8.6.0 | 18 / 6 | |
| 8.5.0 | 18 / 6 | |
| 8.4.1 | 18 / 6 | |
| 8.4.0 | 18 / 6 | |
| 8.3.2 | 18 / 6 | |
| 8.3.1 | 18 / 6 | |
| 8.3.0 | 18 / 6 | |
| 8.2.4 | 18 / 6 | |
| 8.2.3 | 18 / 6 | |
| 8.2.1 | 18 / 6 | |
| 8.2.0 | 18 / 6 | |
| 8.1.3 | 18 / 6 | |
| 8.1.2 | 18 / 6 | |
| 8.1.1 | 18 / 6 | |
| 8.1.0 | 18 / 6 | |
| 8.0.0 | 18 / 6 | |
| 7.3.9 | 18 / 6 | |
| 7.3.8 | 18 / 6 | |
| 7.3.7 | 18 / 6 | |
| 7.3.6 | 18 / 6 | |
| 7.3.5 | 18 / 6 | |
| 7.3.4 | 18 / 6 | |
| 7.3.3 | 18 / 6 | |
| 7.3.2 | 18 / 6 | |
| 7.3.1 | 18 / 6 | |
| 7.3.0 | 18 / 6 | |
| 7.2.0 | 18 / 6 | |
| 7.1.1 | 18 / 6 | |
| 7.0.2 | 18 / 6 | |
| 7.0.1 | 18 / 6 | |
| 7.0.0 | 18 / 6 |
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.7.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.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.6.3
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.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.3.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.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.2.2
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
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.2.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.1.5
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published 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.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.1.0
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.
v9.0.0
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.2
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.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.18.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.17.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.17.4
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.17.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.17.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.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.16.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.15.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.15.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.15.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.15.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.15.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.15.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.15.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.14.2
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.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.