@ezs/core
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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): New files are build output (babel src->lib); no material dep/script changes vs prior approved version. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived package with 182 versions and established publisher; dormancy gap alone is insufficient signal given clean diff. | ai | |
| dependencies | unvetted-dep:autocast | AI (dependencies): Small utility dep, stable across many versions of this package, no known advisories. | ai | |
| dependencies | unvetted-dep:validatorjs | AI (dependencies): Validation library, stable pinned version, no known advisories. | ai | |
| dependencies | unvetted-dep:stream-write | AI (dependencies): Tiny stream helper, stable pinned version, no known advisories. | ai | |
| dependencies | unvetted-dep:concurrent-queue | AI (dependencies): Queue utility, stable pinned version, no known advisories. | ai | |
| phantom-deps | phantom-dep:app-module-path | AI (phantom-deps): app-module-path is a declared dep used for module path configuration; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @ezs/core in established Inist-CNRS monorepo; no relation to the cors package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Intentional encode/decode utility in a stream-transformer framework; not obfuscation. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Explicit decode statement in statements/decode.js; legitimate data transformation feature. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Plugin-loader pattern in a documented plugin system; stable across versions. | ai | |
| phantom-deps | phantom-dep:picomatch | AI (phantom-deps): picomatch is listed in dependencies and used in config/glob matching; phantom-dep heuristic false positive. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4.2.4 | 34 / 0 | |
| 4.2.3 | 34 / 0 | |
| 4.2.2 | 34 / 0 | |
| 4.2.1 | 34 / 0 | |
| 4.2.0 | 34 / 0 | |
| 4.1.4 | 34 / 0 | |
| 4.1.3 | 34 / 0 | |
| 4.1.2 | 34 / 0 | |
| 4.1.1 | 34 / 0 | |
| 4.1.0 | 34 / 0 | |
| 4.0.5 | 34 / 0 | |
| 4.0.4 | 34 / 0 | |
| 4.0.3 | 34 / 0 | |
| 4.0.2 | 34 / 0 | |
| 4.0.1 | 34 / 0 | |
| 4.0.0 | 34 / 0 |
v4.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
2 findingsPackage name '@ezs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
2 findingsPackage name '@ezs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
2 findingsPackage name '@ezs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.