myst-to-react
[](https://www.npmjs.com/package/myst-to-react) [](https://github.com/jupyter-book/myst-theme/blob/main/LICENSE)
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): Monorepo build config reference; not a real import gap for this package. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Monorepo build config reference; stable false positive. | ai | |
| phantom-deps | phantom-dep:myst-config | AI (phantom-deps): Monorepo build config reference; stable false positive. | ai | |
| phantom-deps | phantom-dep:unist-util-visit | AI (phantom-deps): Monorepo build config reference; stable false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Component package in a large monorepo; sparse README and no keywords are expected for internal packages. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.3.1 | 15 / 1 | |
| 1.3.0 | 15 / 1 | |
| 1.1.2 | 15 / 1 | |
| 1.1.1 | 15 / 1 | |
| 1.0.1 | 15 / 1 | |
| 1.0.0 | 14 / 1 | |
| 0.18.0 | 14 / 1 |
v1.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.