@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, so a manually published version cannot be tied back to a reviewed commit.
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 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 0.3.23 | 9 / 4 | |
| 0.3.22 | 9 / 4 | |
| 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 | |
| 0.3.8 | 9 / 4 | |
| 0.3.7 | 9 / 4 | |
| 0.3.6 | 10 / 4 | |
| 0.3.5 | 10 / 4 | |
| 0.3.4 | 10 / 4 | |
| 0.3.3 | 11 / 4 | |
| 0.3.2 | 11 / 4 | |
| 0.3.1 | 11 / 4 | |
| 0.3.0 | 11 / 4 | |
| 0.2.25 | 11 / 4 | |
| 0.2.24 | 11 / 4 | |
| 0.2.23 | 11 / 4 | |
| 0.2.22 | 11 / 4 | |
| 0.2.21 | 11 / 4 | |
| 0.2.20 | 11 / 4 | |
| 0.2.19 | 11 / 4 | |
| 0.2.18 | 11 / 4 | |
| 0.2.17 | 11 / 4 | |
| 0.2.16 | 11 / 4 | |
| 0.2.15 | 11 / 4 | |
| 0.2.14 | 11 / 3 | |
| 0.2.13 | 11 / 3 | |
| 0.2.12 | 11 / 3 | |
| 0.2.11 | 11 / 3 | |
| 0.2.10 | 10 / 3 | |
| 0.2.9 | 11 / 4 | |
| 0.2.8 | 11 / 4 | |
| 0.2.7 | 11 / 4 | |
| 0.2.6 | 11 / 4 | |
| 0.2.5 | 11 / 4 | |
| 0.2.4 | 11 / 4 | |
| 0.2.3 | 11 / 4 | |
| 0.2.2 | 11 / 4 | |
| 0.2.1 | 11 / 4 | |
| 0.2.0 | 12 / 4 | |
| 0.1.3 | 12 / 4 | |
| 0.1.2 | 12 / 4 |
v0.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
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.2.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.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.