@cdc/markup-include
React component for displaying HTML content from an outside link
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:chroma | AI (phantom-deps): Declared in package.json as a dependency; phantom-dep heuristic fires but it may be used indirectly via config or peer usage in this monorepo package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Monorepo build config reference; not a real import gap for this package. | ai | |
| phantom-deps | phantom-dep:react-accessible-accordion | AI (phantom-deps): Monorepo build config reference; not a real import gap for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.26.5 | 5 / 5 | |
| 4.26.4 | 5 / 5 | |
| 4.26.3 | 5 / 5 | |
| 4.26.2 | 5 / 5 | |
| 4.26.1 | 6 / 5 | |
| 4.25.11 | 6 / 4 | |
| 4.25.10 | 6 / 5 | |
| 4.25.8 | 5 / 0 | |
| 4.25.7 | 5 / 0 | |
| 4.25.6 | 5 / 0 |
v4.26.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.26.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.25.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.25.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.25.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.