@quartzds/remark-preset
Remark preset for Quartz design system packages
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:remark-lint-no-unneeded-full-reference-image | AI (dependencies): Well-known remark-lint plugin; stable false positive for this preset package. | ai | |
| dependencies | unvetted-dep:remark-validate-links | AI (dependencies): Well-known remark ecosystem plugin; stable false positive for this preset package. | ai | |
| dependencies | unvetted-dep:remark-lint-no-empty-url | AI (dependencies): Well-known remark-lint plugin; stable false positive for this preset package. | ai | |
| dependencies | unvetted-dep:remark-lint-no-duplicate-defined-urls | AI (dependencies): Well-known remark-lint plugin; stable false positive for this preset package. | ai | |
| dependencies | unvetted-dep:remark-lint-no-heading-like-paragraph | AI (dependencies): Well-known remark-lint plugin; stable false positive for this preset package. | ai | |
| dependencies | unvetted-dep:remark-lint-no-unneeded-full-reference-link | AI (dependencies): Well-known remark-lint plugin; stable false positive for this preset package. | ai | |
| provenance | no-provenance | AI (provenance): Org-published tooling package; lack of provenance is common and no other risk signals present. | ai | |
| phantom-deps | phantom-dep:remark-mdx | AI (phantom-deps): remark-mdx is explicitly declared as a dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.1.3 | 16 / 0 | |
| 2.1.2 | 16 / 0 | |
| 2.1.1 | 16 / 10 | |
| 2.1.0 | 16 / 9 | |
| 2.0.3 | 16 / 10 | |
| 2.0.2 | 16 / 10 | |
| 2.0.1 | 16 / 10 | |
| 2.0.0 | 16 / 10 |
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.