@open-keystone/fields-markdown
KeystoneJS Markdown Field Type
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 | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present for this package. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): prop-types is a common peer/config-only reference in React component packages; not a real risk. | ai | |
| phantom-deps | phantom-dep:@open-arch-ui/input | AI (phantom-deps): Part of the same monorepo ecosystem; config-file reference is expected, not a supply-chain concern. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 7.0.19 | 13 / 1 | |
| 7.0.18 | 13 / 1 | |
| 7.0.17 | 13 / 1 | |
| 7.0.9 | 13 / 1 | |
| 7.0.6 | 13 / 1 | |
| 7.0.5 | 13 / 1 | |
| 7.0.4 | 13 / 1 | |
| 7.0.3 | 13 / 1 | |
| 7.0.2 | 13 / 1 | |
| 7.0.1 | 13 / 1 | |
| 7.0.0 | 13 / 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.9
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.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.