@alloy-js/markdown
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher is GitHub Actions with SLSA attestation; CI/CD publishing is the documented pattern for this Microsoft-affiliated monorepo. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft-affiliated package by a known publisher; lack of Sigstore provenance is common and not a risk indicator for this package. | ai | |
| dependencies | unvetted-dep:@alloy-js/core | AI (dependencies): @alloy-js/core is a sibling package in the same monorepo by the same author; the version pin matches this package's own version, consistent with coordinated releases. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.23.0 | 2 / 5 | |
| 0.22.0 | 2 / 5 | |
| 0.21.0 | 2 / 5 | |
| 0.20.0 | 2 / 5 | |
| 0.19.0 | 2 / 5 | |
| 0.18.0 | 2 / 5 | |
| 0.17.0 | 2 / 5 | |
| 0.16.0 | 2 / 5 | |
| 0.15.1 | 1 / 5 | |
| 0.15.0 | 1 / 5 | |
| 0.14.0 | 1 / 5 |
v0.23.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-28. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.