check-error
Error comparison and information related utility for node and the browser
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): chaijs migrated to GitHub Actions CI/CD publishing with SLSA attestation; publisher=GitHub Actions is the expected and more secure pattern for this org going forward. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of keithamus is consistent with chaijs org transitioning to automated CI/CD releases; repo URL and org ownership unchanged. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): check-error is a stable, mature chaijs utility; long dormancy followed by a CI/CD tooling update is expected behavior for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.1.3 | 0 / 5 | |
| 2.1.1 | 0 / 11 | |
| 2.1.0 | 0 / 14 | |
| 2.0.0 | 0 / 14 | |
| 1.0.3 | 1 / 21 | |
| 1.0.2 | 0 / 21 | |
| 1.0.1 | 0 / 21 | |
| 1.0.0 | 0 / 21 |
v2.1.3
2 findingsThis version was published by a different npm account than previous versions on 2026-01-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-05-08. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-09-27. This could indicate a legitimate maintainer transition or an account compromise.
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.