@casbin/expression-eval
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 | obfuscated-file:dist/expression-eval.js | AI (source-diff): Microbundle minified output; standard for this package's build pipeline. | ai | |
| source-diff | obfuscated-file:dist/expression-eval.modern.js | AI (source-diff): Microbundle minified output; standard for this package's build pipeline. | ai | |
| source-diff | obfuscated-file:dist/expression-eval.module.js | AI (source-diff): Microbundle minified output; standard for this package's build pipeline. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 5.3.0 | 1 / 10 | |
| 5.2.0 | 1 / 10 | |
| 5.1.0 | 1 / 10 | |
| 5.0.2 | 1 / 10 |
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.