@strapi/plugin-users-permissions
Protect your API with a full-authentication process based on JWT
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects v4→v5 major version transition; expected for Strapi monorepo packages. | ai | |
| provenance | publisher-changed | AI (provenance): Both publishers are established Strapi org members; rotation is expected in a large team. | ai | |
| dependencies | unvetted-dep:grant-koa | AI (dependencies): grant-koa is a well-known OAuth middleware for Koa; expected dependency for an auth plugin. | ai | |
| dependencies | unvetted-dep:jwk-to-pem | AI (dependencies): jwk-to-pem is a standard JWT/JWK utility; appropriate for a JWT-based auth plugin. | ai | |
| dependencies | unvetted-dep:react-query | AI (dependencies): react-query is a widely-used data-fetching library; legitimate UI dependency for Strapi admin panel. | ai | |
| dependencies | unvetted-dep:@strapi/icons | AI (dependencies): First-party Strapi icon library from the same monorepo; no security concern. | ai | |
| dependencies | unvetted-dep:purest | AI (dependencies): purest is a legitimate OAuth REST client library appropriate for a users-permissions plugin; not a security concern. | ai | |
| dependencies | unvetted-dep:koa2-ratelimit | AI (dependencies): koa2-ratelimit is a standard rate-limiting middleware; appropriate for an auth plugin. | ai | |
| dependencies | unvetted-dep:@strapi/design-system | AI (dependencies): First-party Strapi design system from the same monorepo; no security concern. | ai | |
| dependencies | unvetted-dep:@strapi/helper-plugin | AI (dependencies): First-party Strapi helper plugin from the same monorepo; no security concern. | ai | |
| phantom-deps | phantom-dep:koa | AI (phantom-deps): koa is a declared direct dependency in package.json; phantom-dep finding is a false positive for this plugin architecture. | ai | |
| phantom-deps | phantom-dep:react-redux | AI (phantom-deps): react-redux is a declared direct dependency in package.json; phantom-dep finding is a false positive for this plugin architecture. | ai | |
| provenance | no-provenance | AI (provenance): Established Strapi core package with 164k weekly downloads and 1730 days of history; lack of provenance is not a meaningful risk signal here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Strapi monorepo sub-package; README and keywords are minimal by design, documentation lives in the main Strapi docs site. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Standard Strapi license declaration referencing their LICENSE file; consistent across all Strapi packages. | ai |
Versions (showing 51 of 65)
| Version | Deps | Published |
|---|---|---|
| 5.47.1 | 20 / 9 | |
| 5.47.0 | 20 / 9 | |
| 5.46.1 | 20 / 9 | |
| 5.46.0 | 20 / 9 | |
| 5.45.1 | 20 / 9 | |
| 5.45.0 | 20 / 9 | |
| 5.44.0 | 20 / 9 | |
| 5.43.0 | 20 / 9 | |
| 5.42.1 | 20 / 9 | |
| 5.42.0 | 20 / 9 | |
| 5.41.1 | 20 / 9 | |
| 5.41.0 | 20 / 9 | |
| 5.40.0 | 20 / 9 | |
| 5.39.0 | 20 / 9 | |
| 5.38.1 | 20 / 9 | |
| 5.38.0 | 20 / 9 | |
| 5.37.1 | 20 / 9 | |
| 5.37.0 | 20 / 9 | |
| 5.36.1 | 20 / 9 | |
| 5.36.0 | 20 / 9 | |
| 5.35.0 | 20 / 9 | |
| 5.34.0 | 20 / 9 | |
| 5.33.4 | 20 / 9 | |
| 5.33.3 | 20 / 9 | |
| 5.33.2 | 20 / 9 | |
| 5.33.1 | 20 / 9 | |
| 5.33.0 | 20 / 9 | |
| 5.32.0 | 20 / 9 | |
| 5.31.3 | 20 / 9 | |
| 5.31.2 | 20 / 9 | |
| 5.31.1 | 20 / 9 | |
| 5.31.0 | 20 / 9 | |
| 5.30.1 | 20 / 9 | |
| 5.30.0 | 20 / 9 | |
| 5.29.0 | 20 / 9 | |
| 5.28.0 | 20 / 9 | |
| 5.27.0 | 20 / 9 | |
| 5.26.0 | 20 / 9 | |
| 5.25.0 | 20 / 9 | |
| 5.24.2 | 20 / 9 | |
| 5.24.1 | 20 / 9 | |
| 5.24.0 | 20 / 9 | |
| 5.23.6 | 20 / 9 | |
| 5.23.5 | 20 / 9 | |
| 5.23.4 | 20 / 9 | |
| 5.23.3 | 20 / 9 | |
| 5.23.2 | 20 / 9 | |
| 5.23.1 | 20 / 9 | |
| 5.23.0 | 20 / 9 | |
| 5.22.0 | 20 / 9 | |
| 5.21.0 | 20 / 9 |
v5.47.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.47.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.46.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.45.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.42.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.42.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.41.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.41.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.40.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.39.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.38.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.38.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.37.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.37.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.36.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.36.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.35.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.34.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.33.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.33.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.33.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.33.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.33.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.32.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.31.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.31.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.31.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.31.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.30.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.30.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.22.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.21.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.