@marcbachmann/cel-js
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
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 7.6.1 | 0 / 2 | |
| 7.6.0 | 0 / 2 | |
| 7.5.3 | 0 / 2 | |
| 7.5.2 | 0 / 2 | |
| 7.5.1 | 0 / 2 | |
| 7.5.0 | 0 / 2 | |
| 7.4.0 | 0 / 2 | |
| 7.3.1 | 0 / 2 | |
| 7.3.0 | 0 / 2 | |
| 7.2.4 | 0 / 2 | |
| 7.2.3 | 0 / 2 | |
| 7.2.2 | 0 / 2 | |
| 7.2.1 | 0 / 2 | |
| 7.2.0 | 0 / 2 | |
| 7.1.0 | 0 / 2 | |
| 7.0.4 | 0 / 2 | |
| 7.0.3 | 0 / 2 | |
| 7.0.2 | 0 / 2 | |
| 7.0.1 | 0 / 2 | |
| 7.0.0 | 0 / 2 | |
| 6.5.1 | 0 / 2 | |
| 6.5.0 | 0 / 2 | |
| 6.4.0 | 0 / 2 | |
| 6.3.4 | 0 / 2 | |
| 6.3.3 | 0 / 2 | |
| 6.3.2 | 0 / 2 | |
| 6.3.1 | 0 / 2 | |
| 6.3.0 | 0 / 2 | |
| 6.2.0 | 0 / 2 | |
| 6.1.0 | 0 / 2 | |
| 6.0.2 | 0 / 2 | |
| 6.0.1 | 0 / 2 | |
| 6.0.0 | 0 / 2 | |
| 5.2.1 | 0 / 2 | |
| 5.2.0 | 0 / 2 | |
| 5.1.0 | 0 / 2 | |
| 5.0.0 | 0 / 2 | |
| 4.2.4 | 0 / 2 | |
| 4.2.3 | 0 / 2 | |
| 4.2.2 | 0 / 2 | |
| 4.2.1 | 0 / 2 | |
| 4.2.0 | 0 / 2 | |
| 4.1.1 | 0 / 2 | |
| 4.1.0 | 0 / 2 | |
| 4.0.0 | 0 / 2 |
v7.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.