chai-exclude
Exclude keys to compare from a deep equal operation with chai expect and assert
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): chai-exclude has always been published without provenance by its original author; this is stable for this package. | ai | |
| provenance | missing-githead | AI (provenance): Missing gitHead reflects a local publish environment change, not a security concern for this long-standing single-maintainer package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 1 / 4 | |
| 3.0.0 | 1 / 4 | |
| 2.1.1 | 1 / 5 | |
| 2.1.0 | 1 / 5 | |
| 2.0.3 | 1 / 5 | |
| 2.0.2 | 1 / 5 | |
| 2.0.1 | 1 / 5 | |
| 2.0.0 | 1 / 5 | |
| 1.0.12 | 1 / 4 | |
| 1.0.11 | 1 / 4 | |
| 1.0.10 | 1 / 9 | |
| 1.0.9 | 0 / 9 | |
| 1.0.8 | 0 / 9 | |
| 1.0.7 | 0 / 9 | |
| 1.0.6 | 0 / 9 | |
| 1.0.5 | 0 / 9 | |
| 1.0.4 | 0 / 9 | |
| 1.0.3 | 0 / 9 | |
| 1.0.2 | 0 / 9 | |
| 1.0.1 | 0 / 9 | |
| 1.0.0 | 0 / 8 |
v3.0.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mesaugat.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mesaugat.
v2.1.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mesaugat.
v2.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mesaugat.
v2.0.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mesaugat.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.