@docusaurus/remark-plugin-npm2yarn
Remark plugin for converting npm commands to Yarn commands as tabs.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:npm-to-yarn | AI (dependencies): npm-to-yarn is the core utility this plugin wraps; its use is intentional and expected across all versions. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 3.10.2 | 5 / 4 | |
| 3.10.1 | 5 / 4 | |
| 3.10.0 | 5 / 4 | |
| 3.9.2 | 5 / 4 | |
| 3.9.1 | 5 / 4 | |
| 3.9.0 | 5 / 4 | |
| 3.8.1 | 5 / 4 | |
| 3.8.0 | 5 / 4 | |
| 3.7.0 | 5 / 4 | |
| 3.6.3 | 5 / 4 | |
| 3.6.2 | 5 / 4 | |
| 3.6.1 | 5 / 4 | |
| 3.6.0 | 5 / 4 | |
| 3.5.2 | 5 / 4 | |
| 3.5.1 | 5 / 4 | |
| 3.5.0 | 5 / 4 | |
| 3.4.0 | 5 / 4 | |
| 3.3.2 | 5 / 4 | |
| 3.3.0 | 5 / 4 | |
| 3.2.1 | 5 / 4 | |
| 3.2.0 | 5 / 4 | |
| 3.1.1 | 5 / 4 | |
| 3.1.0 | 5 / 4 | |
| 3.0.1 | 5 / 4 | |
| 3.0.0 | 5 / 4 |
v3.10.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.