@backstage/plugin-scaffolder-backend-module-confluence-to-markdown
The confluence-to-markdown module for @backstage/plugin-scaffolder-backend
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:node-html-markdown | AI (dependencies): node-html-markdown is a legitimate, widely-used HTML-to-Markdown library; its use is consistent with this package's purpose of converting Confluence content to Markdown. | ai | |
| provenance | no-provenance | AI (provenance): Backstage publishes many packages without Sigstore provenance; this is consistent across the entire @backstage scope and not a risk indicator for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.3.21 | 9 / 4 | |
| 0.3.20 | 9 / 4 | |
| 0.3.19 | 9 / 4 | |
| 0.3.18 | 9 / 4 | |
| 0.3.16 | 9 / 4 | |
| 0.3.15 | 9 / 4 | |
| 0.3.14 | 9 / 4 | |
| 0.3.13 | 9 / 4 | |
| 0.3.12 | 9 / 4 | |
| 0.3.11 | 9 / 4 | |
| 0.3.10 | 9 / 4 | |
| 0.3.9 | 9 / 4 |
v0.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.