casbin
An authorization library that supports access control models like ACL, RBAC, ABAC in Node.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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
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): Dual build (cjs/esm) output; legitimate for this package's refactor. | ai | |
| dependencies | unvetted-dep:@casbin/expression-eval | AI (dependencies): First-party scoped package under the casbin org; stable dependency across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established Apache project; provenance absence is common and not a risk signal here. | ai |
Versions (showing 100 of 104)
| Version | Deps | Published |
|---|---|---|
| 5.51.1 | 5 / 25 | |
| 5.51.0 | 5 / 24 | |
| 5.50.0 | 5 / 24 | |
| 5.49.0 | 5 / 25 | |
| 5.48.0 | 5 / 25 | |
| 5.47.0 | 5 / 25 | |
| 5.46.0 | 5 / 25 | |
| 5.45.3 | 5 / 25 | |
| 5.45.2 | 5 / 25 | |
| 5.45.1 | 5 / 25 | |
| 5.45.0 | 5 / 25 | |
| 5.44.0 | 5 / 25 | |
| 5.43.0 | 5 / 27 | |
| 5.42.0 | 5 / 27 | |
| 5.41.0 | 5 / 27 | |
| 5.40.0 | 5 / 27 | |
| 5.39.0 | 5 / 27 | |
| 5.38.0 | 5 / 27 | |
| 5.37.0 | 5 / 27 | |
| 5.36.0 | 5 / 27 | |
| 5.35.0 | 5 / 27 | |
| 5.34.0 | 5 / 27 | |
| 5.32.0 | 5 / 27 | |
| 5.31.0 | 5 / 27 | |
| 5.30.0 | 5 / 27 | |
| 5.29.0 | 5 / 27 | |
| 5.28.0 | 5 / 27 | |
| 5.27.1 | 5 / 27 | |
| 5.27.0 | 5 / 27 | |
| 5.26.2 | 5 / 27 | |
| 5.26.1 | 5 / 27 | |
| 5.26.0 | 5 / 27 | |
| 5.25.0 | 5 / 27 | |
| 5.24.4 | 5 / 27 | |
| 5.24.3 | 5 / 27 | |
| 5.24.2 | 4 / 27 | |
| 5.24.1 | 4 / 27 | |
| 5.24.0 | 4 / 28 | |
| 5.23.2 | 4 / 28 | |
| 5.23.1 | 4 / 28 | |
| 5.23.0 | 4 / 28 | |
| 5.22.0 | 4 / 28 | |
| 5.21.0 | 4 / 28 | |
| 5.20.4 | 4 / 28 | |
| 5.20.3 | 4 / 28 | |
| 5.20.2 | 4 / 28 | |
| 5.20.1 | 4 / 28 | |
| 5.20.0 | 4 / 28 | |
| 5.19.3 | 4 / 28 | |
| 5.19.2 | 4 / 28 | |
| 5.19.1 | 4 / 28 | |
| 5.19.0 | 4 / 28 | |
| 5.18.0 | 4 / 28 | |
| 5.17.0 | 4 / 28 | |
| 5.16.0 | 4 / 28 | |
| 5.15.2 | 4 / 28 | |
| 5.15.1 | 4 / 28 | |
| 5.15.0 | 4 / 28 | |
| 5.14.0 | 4 / 28 | |
| 5.13.2 | 4 / 28 | |
| 5.13.1 | 4 / 28 | |
| 5.13.0 | 4 / 28 | |
| 5.12.0 | 4 / 28 | |
| 5.11.5 | 4 / 28 | |
| 5.11.4 | 4 / 28 | |
| 5.11.3 | 4 / 28 | |
| 5.11.2 | 4 / 28 | |
| 5.11.1 | 4 / 28 | |
| 5.11.0 | 4 / 28 | |
| 5.10.0 | 4 / 28 | |
| 5.9.1 | 4 / 28 | |
| 5.9.0 | 4 / 28 | |
| 5.8.0 | 4 / 28 | |
| 5.7.2 | 4 / 28 | |
| 5.7.1 | 4 / 28 | |
| 5.7.0 | 4 / 28 | |
| 5.6.3 | 4 / 28 | |
| 5.6.2 | 4 / 28 | |
| 5.6.1 | 5 / 29 | |
| 5.6.0 | 5 / 29 | |
| 5.5.0 | 5 / 29 | |
| 5.4.2 | 5 / 29 | |
| 5.4.1 | 4 / 29 | |
| 5.4.0 | 4 / 29 | |
| 5.3.1 | 4 / 29 | |
| 5.2.3 | 4 / 25 | |
| 5.2.2 | 4 / 25 | |
| 5.2.1 | 4 / 25 | |
| 5.2.0 | 4 / 25 | |
| 5.1.6 | 4 / 25 | |
| 5.1.5 | 4 / 25 | |
| 5.1.4 | 4 / 25 | |
| 5.1.3 | 4 / 25 | |
| 5.1.2 | 4 / 25 | |
| 5.1.1 | 4 / 25 | |
| 5.1.0 | 4 / 25 | |
| 5.0.7 | 4 / 25 | |
| 5.0.6 | 4 / 24 | |
| 5.0.5 | 4 / 24 | |
| 5.0.4 | 4 / 24 |
v5.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.26.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.26.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (zxilly) than the most recent previously approved version (nodece) on 2021-06-15, but zxilly is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
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: nodece.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.