@strapi/openapi
A tool set to help generate and validate API documentation for Strapi projects
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (nico-strapi, strapi.adzouz) are clearly Strapi org members; routine team changes. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal is part of normal Strapi team rotation. | ai | |
| provenance | publisher-changed | AI (provenance): bassel17 is a legitimate Strapi org publisher with 10 approved packages; scoped @strapi namespace requires org access. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Strapi monorepo sub-package; short README and no keywords are normal for internal packages in a large monorepo. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Standard Strapi license pattern pointing to LICENSE file in repo; stable across all @strapi packages. | ai |
Versions (showing 52 of 52)
| Version | Deps | Published |
|---|---|---|
| 5.47.1 | 3 / 2 | |
| 5.47.0 | 3 / 2 | |
| 5.46.1 | 3 / 2 | |
| 5.46.0 | 3 / 2 | |
| 5.45.1 | 3 / 2 | |
| 5.45.0 | 3 / 2 | |
| 5.44.0 | 3 / 2 | |
| 5.43.0 | 3 / 2 | |
| 5.42.1 | 3 / 2 | |
| 5.42.0 | 3 / 2 | |
| 5.41.1 | 3 / 2 | |
| 5.41.0 | 3 / 2 | |
| 5.40.0 | 3 / 2 | |
| 5.39.0 | 3 / 2 | |
| 5.38.1 | 3 / 2 | |
| 5.38.0 | 3 / 2 | |
| 5.37.1 | 3 / 2 | |
| 5.37.0 | 3 / 2 | |
| 5.36.1 | 3 / 2 | |
| 5.36.0 | 3 / 2 | |
| 5.35.0 | 3 / 2 | |
| 5.34.0 | 3 / 2 | |
| 5.33.4 | 3 / 2 | |
| 5.33.3 | 3 / 2 | |
| 5.33.2 | 3 / 2 | |
| 5.33.1 | 3 / 2 | |
| 5.33.0 | 3 / 2 | |
| 5.32.0 | 3 / 2 | |
| 5.31.3 | 3 / 2 | |
| 5.31.2 | 3 / 2 | |
| 5.31.1 | 3 / 2 | |
| 5.31.0 | 3 / 2 | |
| 5.30.1 | 3 / 2 | |
| 5.30.0 | 3 / 2 | |
| 5.29.0 | 3 / 2 | |
| 5.28.0 | 3 / 2 | |
| 5.27.0 | 3 / 2 | |
| 5.26.0 | 3 / 2 | |
| 5.25.0 | 3 / 2 | |
| 5.24.2 | 3 / 2 | |
| 5.24.1 | 3 / 2 | |
| 5.24.0 | 3 / 2 | |
| 5.23.6 | 3 / 2 | |
| 5.23.5 | 3 / 2 | |
| 5.23.4 | 3 / 2 | |
| 5.23.3 | 3 / 2 | |
| 5.23.2 | 3 / 2 | |
| 5.23.1 | 3 / 2 | |
| 5.23.0 | 3 / 2 | |
| 5.22.0 | 3 / 2 | |
| 5.21.0 | 3 / 2 | |
| 5.20.0 | 4 / 2 |
v5.47.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.45.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.45.0
1 findingPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.41.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.40.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-18. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.39.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.38.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.38.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-04. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.37.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.37.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.36.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-18. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.36.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.35.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-04. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.34.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-28. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.4
2 findingsThis version was published by a different npm account than previous versions on 2026-01-21. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.3
2 findingsThis version was published by a different npm account than previous versions on 2026-01-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.2
2 findingsThis version was published by a different npm account than previous versions on 2026-01-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.1
2 findingsThis version was published by a different npm account than previous versions on 2025-12-29. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.32.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.