@uwdata/mosaic-plot
A Mosaic-powered plotting framework based on Observable Plot.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): jheer→domoritz is a known UW IDL lab handoff; both are established researchers on the same project. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): domoritz is a co-author of the mosaic project; addition is a legitimate org-level transition. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @uwdata/flechette is from the same @uwdata org scope; consistent with the project's own ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): Established package; provenance not used by this publisher across all versions. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.26.0 | 5 / 0 | |
| 0.25.0 | 5 / 0 | |
| 0.24.4 | 5 / 0 | |
| 0.24.3 | 5 / 0 | |
| 0.24.2 | 5 / 0 | |
| 0.24.1 | 5 / 0 | |
| 0.24.0 | 5 / 0 | |
| 0.23.1 | 5 / 0 | |
| 0.23.0 | 5 / 0 | |
| 0.22.0 | 4 / 0 | |
| 0.21.1 | 4 / 0 | |
| 0.21.0 | 4 / 0 | |
| 0.20.1 | 4 / 0 | |
| 0.20.0 | 4 / 0 | |
| 0.19.1 | 4 / 0 | |
| 0.19.0 | 4 / 0 | |
| 0.18.0 | 4 / 0 | |
| 0.17.0 | 4 / 0 | |
| 0.16.2 | 4 / 0 | |
| 0.16.1 | 4 / 0 |
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
2 findingsThis version was published by a different npm account than previous versions on 2026-04-04. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.