@metamask/docusaurus-openrpc
A Docusaurus plugin for generating interactive documentation from your OpenRPC document
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:docusaurus-open-rpc-docs-react | AI (dependencies): Sibling package in same OpenRPC docs ecosystem, used as intended peer for docs rendering. | ai | |
| phantom-deps | phantom-dep:@docusaurus/plugin-content-docs | AI (phantom-deps): Used via Docusaurus config/plugin system, not direct import; expected pattern. | ai | |
| phantom-deps | phantom-dep:process | AI (phantom-deps): process is a declared runtime dep used as a webpack polyfill, not a phantom dep issue. | ai | |
| phantom-deps | phantom-dep:@docusaurus/core | AI (phantom-deps): @docusaurus/core is a peer dependency; phantom-dep heuristic fires incorrectly for peer deps. | ai | |
| provenance | no-provenance | AI (provenance): MetaMask org package; lack of provenance is common and not a disqualifier here. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.4.1 | 17 / 37 | |
| 0.4.0 | 18 / 32 | |
| 0.3.1 | 18 / 32 | |
| 0.2.2 | 18 / 32 | |
| 0.2.1 | 18 / 32 | |
| 0.2.0 | 18 / 32 | |
| 0.1.1 | 18 / 32 | |
| 0.1.0 | 18 / 32 | |
| 0.0.13 | 5 / 32 | |
| 0.0.10 | 5 / 32 | |
| 0.0.6 | 5 / 32 | |
| 0.0.5 | 3 / 32 | |
| 0.0.4 | 3 / 32 | |
| 0.0.3 | 3 / 31 |
v0.4.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.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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.
v0.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.