concordance
Compare, format, diff and serialize any JavaScript value
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Established 9-year-old package with clear purpose and repo; missing keywords/README polish are cosmetic and stable for this package. | ai | |
| dependencies | unvetted-dep:function-name-support | AI (dependencies): function-name-support is a legitimate small utility for detecting JS engine function name support, appropriate for a value comparison/formatting library. | ai | |
| dependencies | unvetted-dep:md5-hex | AI (dependencies): md5-hex is a legitimate, well-known npm package used for MD5 hashing; its use here is appropriate and stable across versions of concordance. | ai | |
| dependencies | unvetted-dep:lodash.islength | AI (dependencies): lodash.islength is a standard lodash modular utility; its use alongside other lodash modules in this package is expected and benign. | ai | |
| provenance | no-provenance | AI (provenance): Established package with a known maintainer and public GitHub repo; lack of Sigstore provenance is not a meaningful risk signal here. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 5.0.4 | 8 / 12 | |
| 5.0.3 | 8 / 12 | |
| 5.0.2 | 8 / 12 | |
| 5.0.1 | 8 / 12 | |
| 5.0.0 | 8 / 12 | |
| 4.0.0 | 11 / 8 | |
| 3.0.0 | 11 / 10 | |
| 2.0.0 | 11 / 10 | |
| 1.0.0 | 11 / 11 | |
| 0.9.0 | 11 / 11 | |
| 0.8.0 | 11 / 11 | |
| 0.7.0 | 9 / 11 | |
| 0.6.0 | 9 / 11 | |
| 0.5.0 | 8 / 9 | |
| 0.4.0 | 6 / 9 |
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
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.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.