@breadstone-tools/markdowner-app
Markdowner cli
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Breadstone org packages consistently lack provenance; stable false positive for this package family. | ai |
Versions (showing 51 of 315)
| Version | Deps | Published |
|---|---|---|
| 0.1.61 | 4 / 0 | |
| 0.1.59 | 4 / 0 | |
| 0.1.58 | 3 / 0 | |
| 0.1.57 | 3 / 0 | |
| 0.1.56 | 3 / 0 | |
| 0.1.55 | 3 / 0 | |
| 0.1.54 | 3 / 0 | |
| 0.1.53 | 3 / 0 | |
| 0.1.52 | 3 / 0 | |
| 0.1.51 | 3 / 0 | |
| 0.1.50 | 3 / 0 | |
| 0.1.49 | 3 / 0 | |
| 0.1.48 | 3 / 0 | |
| 0.1.47 | 3 / 0 | |
| 0.1.46 | 3 / 0 | |
| 0.1.45 | 3 / 0 | |
| 0.1.44 | 3 / 0 | |
| 0.1.43 | 3 / 0 | |
| 0.1.42 | 3 / 0 | |
| 0.1.41 | 3 / 0 | |
| 0.1.40 | 3 / 0 | |
| 0.1.39 | 3 / 0 | |
| 0.1.38 | 3 / 0 | |
| 0.1.37 | 3 / 0 | |
| 0.1.36 | 3 / 0 | |
| 0.1.35 | 3 / 0 | |
| 0.1.33 | 3 / 0 | |
| 0.1.32 | 3 / 0 | |
| 0.1.31 | 3 / 0 | |
| 0.1.30 | 3 / 0 | |
| 0.1.28 | 3 / 0 | |
| 0.1.27 | 3 / 0 | |
| 0.1.26 | 3 / 0 | |
| 0.1.25 | 3 / 0 | |
| 0.1.23 | 3 / 0 | |
| 0.1.22 | 3 / 0 | |
| 0.1.21 | 3 / 0 | |
| 0.1.20 | 3 / 0 | |
| 0.1.19 | 3 / 0 | |
| 0.1.18 | 3 / 0 | |
| 0.1.17 | 3 / 0 | |
| 0.1.16 | 3 / 0 | |
| 0.1.15 | 3 / 0 | |
| 0.1.14 | 3 / 0 | |
| 0.1.13 | 3 / 0 | |
| 0.1.12 | 3 / 0 | |
| 0.1.11 | 3 / 0 | |
| 0.1.10 | 3 / 0 | |
| 0.1.9 | 3 / 0 | |
| 0.1.8 | 3 / 0 | |
| 0.1.7 | 3 / 0 |
v0.1.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.