@canonical/webarchitect
A tool to test the compliance with architecture specifications for packages and applications.
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 change reflects migration to CI/CD publishing (GitHub Actions); SLSA attestation confirms integrity. Stable pattern for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of manual publisher is expected when transitioning to automated CI/CD publishing under the @canonical org. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.32.0 | 3 / 7 | |
| 0.31.0 | 3 / 7 | |
| 0.30.0 | 3 / 7 | |
| 0.29.0 | 3 / 7 | |
| 0.28.0 | 3 / 7 | |
| 0.27.0 | 3 / 7 | |
| 0.26.0 | 3 / 6 | |
| 0.25.0 | 3 / 6 | |
| 0.24.0 | 3 / 6 | |
| 0.23.0 | 3 / 6 | |
| 0.22.0 | 3 / 6 | |
| 0.21.0 | 3 / 6 | |
| 0.20.0 | 3 / 6 | |
| 0.17.1 | 3 / 6 | |
| 0.17.0 | 3 / 6 | |
| 0.16.0 | 3 / 6 | |
| 0.15.1 | 3 / 6 | |
| 0.15.0 | 3 / 6 | |
| 0.14.0 | 3 / 6 | |
| 0.13.0 | 3 / 6 | |
| 0.12.0 | 3 / 5 | |
| 0.11.0 | 3 / 5 | |
| 0.10.0 | 3 / 5 |
v0.32.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.31.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.29.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-03. 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.20.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mariadias143) than the most recent previously approved version (ad.vl) on 2026-03-26, but mariadias143 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ad.vl) than the most recent previously approved version (jmuzina) on 2026-03-03, but ad.vl is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.15.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ad.vl) than the most recent previously approved version (jmuzina) on 2026-02-23, but ad.vl is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.