@strapi/permissions
Strapi's permission layer.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): alexandrebodin is a senior Strapi maintainer (12,955 approved packages, 3,230 days history). Publisher change reflects internal team transition at Strapi Solutions SAS, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects v4→v5 major version transition in Strapi monorepo. v5.x is an active release line; gap is explained by major rewrite, not account takeover. | ai | |
| dependencies | unvetted-dep:@casl/ability | AI (dependencies): @casl/ability is a well-known authorization library; its use in a permissions package is expected and appropriate across all versions of @strapi/permissions. | ai | |
| provenance | no-provenance | AI (provenance): Strapi packages consistently lack Sigstore provenance; this is a stable characteristic of the entire Strapi ecosystem, not a per-version anomaly. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Strapi uses 'SEE LICENSE IN LICENSE' as their standard license declaration across all packages; this is expected and stable for this package. | ai |
Versions (showing 12 of 112)
| Version | Deps | Published |
|---|---|---|
| 5.1.1 | 5 / 3 | |
| 5.1.0 | 5 / 3 | |
| 5.0.6 | 5 / 3 | |
| 5.0.5 | 5 / 3 | |
| 5.0.4 | 5 / 3 | |
| 5.0.3 | 5 / 3 | |
| 5.0.2 | 5 / 3 | |
| 5.0.1 | 5 / 3 | |
| 5.0.0 | 5 / 3 | |
| 4.26.2 | 5 / 3 | |
| 4.26.1 | 5 / 3 | |
| 4.26.0 | 5 / 3 |
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.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.
v5.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.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.