@open-keystone/fields-wysiwyg-tinymce
KeystoneJS WYSIWYG HTML Field Type, powered by TinyMCE
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:react | AI (phantom-deps): Build-output package; react is a peer dep referenced in config, not directly imported in dist. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): Same pattern as react — peer/config reference in a bundled package. | ai | |
| phantom-deps | phantom-dep:@open-arch-ui/input | AI (phantom-deps): Bundled dist package; import may be inlined rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@open-arch-ui/theme | AI (phantom-deps): Same bundled-dist pattern. | ai | |
| phantom-deps | phantom-dep:@primer/octicons-react | AI (phantom-deps): Same bundled-dist pattern. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 7.0.19 | 11 / 1 | |
| 7.0.18 | 11 / 1 | |
| 7.0.17 | 11 / 1 | |
| 7.0.6 | 11 / 1 | |
| 7.0.5 | 11 / 1 | |
| 7.0.4 | 11 / 1 | |
| 7.0.3 | 11 / 1 | |
| 7.0.2 | 11 / 1 | |
| 7.0.1 | 11 / 1 | |
| 7.0.0 | 11 / 1 |
v7.0.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.