docusaurus-theme-openapi-docs
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from human publisher to GitHub Actions CI with SLSA attestation is a legitimate supply chain improvement for this org. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): path-browserify is a standard browser polyfill; appropriate for a Docusaurus browser-side theme. | ai | |
| dependencies | unvetted-dep:postman-collection | AI (dependencies): postman-collection is a well-known Postman library; stable legitimate dependency for this OpenAPI theme. | ai | |
| dependencies | unvetted-dep:postman-code-generators | AI (dependencies): postman-code-generators is a well-known Postman library; stable legitimate dependency for this OpenAPI theme. | ai | |
| phantom-deps | phantom-dep:sass | AI (phantom-deps): sass is a declared runtime dep used via sass-loader config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:unist-util-visit | AI (phantom-deps): unist-util-visit is a declared dep used in remark/rehype pipeline; stable false positive. | ai | |
| phantom-deps | phantom-dep:url | AI (phantom-deps): url is a runtime dep in package.json for browser polyfill; phantom-dep heuristic false positive. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.0.2 | 28 / 13 | |
| 5.0.1 | 28 / 13 | |
| 5.0.0 | 28 / 13 | |
| 4.7.1 | 27 / 13 | |
| 4.7.0 | 27 / 13 | |
| 4.6.0 | 27 / 13 |
v5.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-08. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.