@dxos/plugin-mermaid
Mermaid markdown plugin
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): dxos-bot → GitHub Actions is a CI pipeline migration within the same DXOS org; SLSA attestation confirms build integrity. | ai | |
| source-diff | obfuscated-file:dist/lib/neutral/MermaidPlugin.mjs | AI (source-diff): Standard bundled ESM output from a monorepo build; sample shows readable imports, not malicious obfuscation. | ai | |
| phantom-deps | phantom-dep:@dxos/operation | AI (phantom-deps): Same-org dep; likely used transitively or in build tooling within the monorepo. | ai | |
| bogus-package | bogus-package | AI (bogus-package): DXOS monorepo plugin; sparse README is typical for internal ecosystem packages, not spam. | ai | |
| phantom-deps | phantom-dep:@preact-signals/safe-react | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:effect | AI (phantom-deps): effect is a peer dep declared in peerDependencies; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:@dxos/plugin-space | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo packages. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.9.0 | 12 / 10 | |
| 0.8.3 | 10 / 10 | |
| 0.8.2 | 10 / 10 | |
| 0.8.1 | 8 / 11 | |
| 0.8.0 | 8 / 11 | |
| 0.7.4 | 8 / 11 | |
| 0.7.3 | 8 / 11 | |
| 0.7.2 | 8 / 11 | |
| 0.7.1 | 8 / 11 | |
| 0.7.0 | 8 / 11 | |
| 0.6.13 | 8 / 11 | |
| 0.6.12 | 8 / 11 | |
| 0.6.11 | 8 / 11 | |
| 0.6.10 | 8 / 11 | |
| 0.6.9 | 8 / 11 | |
| 0.6.8 | 8 / 11 |
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.