@vertz/ui-server
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@vertz/core | AI (phantom-deps): Same-org monorepo sibling; declared as runtime dep, may be re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@jridgewell/trace-mapping | AI (phantom-deps): Source-map tooling dep referenced in config files; stable false positive for this build-tool package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.2.80 | 8 / 0 | |
| 0.2.78 | 8 / 0 | |
| 0.2.76 | 8 / 0 | |
| 0.2.75 | 8 / 0 | |
| 0.2.70 | 8 / 0 | |
| 0.2.68 | 8 / 0 | |
| 0.2.66 | 8 / 0 | |
| 0.2.62 | 8 / 0 | |
| 0.2.3 | 7 / 5 | |
| 0.2.0 | 3 / 5 |
v0.2.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.