@voplus/morpho-workspace
morpho workspace module
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:tippy.js | AI (phantom-deps): Declared runtime dep in a workspace bundle; referenced in config files, not a phantom. | ai | |
| phantom-deps | phantom-dep:@fullcalendar/core | AI (phantom-deps): Declared runtime dep alongside other @fullcalendar/* packages; config-only reference is expected for this calendar library. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 10.0.9 | 10 / 20 | |
| 10.0.8 | 10 / 20 | |
| 10.0.5 | 10 / 20 | |
| 10.0.4 | 10 / 20 | |
| 10.0.0 | 10 / 20 | |
| 9.0.19 | 10 / 10 | |
| 9.0.14 | 10 / 10 | |
| 9.0.11 | 10 / 10 | |
| 9.0.8 | 10 / 10 | |
| 9.0.4 | 10 / 10 | |
| 9.0.3 | 10 / 10 | |
| 8.0.1 | 10 / 10 | |
| 7.0.6 | 11 / 10 | |
| 7.0.2 | 11 / 10 | |
| 6.1.80 | 11 / 10 | |
| 6.1.79 | 11 / 10 | |
| 6.1.75 | 11 / 10 | |
| 6.1.68 | 11 / 10 |
v10.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.