@live-change/user-frontend
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:@live-change/vue3-components | AI (phantom-deps): Same-org peer dep; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@live-change/security-frontend | AI (phantom-deps): Same-org peer dep; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:vue-meta | AI (phantom-deps): Frontend framework dep used via config, not direct import. | ai | |
| phantom-deps | phantom-dep:cross-env | AI (phantom-deps): CLI tool used in npm scripts, not imported. | ai | |
| phantom-deps | phantom-dep:pluralize | AI (phantom-deps): Utility dep used in config/template context. | ai | |
| phantom-deps | phantom-dep:compression | AI (phantom-deps): Server middleware dep used in config, not direct import. | ai | |
| phantom-deps | phantom-dep:@vueuse/core | AI (phantom-deps): Frontend framework dep re-exported or used in config. | ai | |
| phantom-deps | phantom-dep:serve-static | AI (phantom-deps): Server dep used in config context. | ai | |
| phantom-deps | phantom-dep:@live-change/dao | AI (phantom-deps): Same-org dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:v-shared-element | AI (phantom-deps): UI plugin dep used in config/plugin registration, not direct import. | ai | |
| phantom-deps | phantom-dep:codeceptjs-assert | AI (phantom-deps): Test helper dep used in test config. | ai | |
| phantom-deps | phantom-dep:sass | AI (phantom-deps): Frontend framework package; deps used in config/build context, not direct imports. | ai | |
| phantom-deps | phantom-dep:serialize-javascript | AI (phantom-deps): SSR utility dep used in config context. | ai | |
| phantom-deps | phantom-dep:@live-change/dao-vue3 | AI (phantom-deps): Same-org dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:unique-names-generator | AI (phantom-deps): Utility dep used in config/test context. | ai | |
| phantom-deps | phantom-dep:codeceptjs-video-helper | AI (phantom-deps): Test helper dep used in test config. | ai | |
| phantom-deps | phantom-dep:rollup-plugin-visualizer | AI (phantom-deps): Build tool dep used in vite/rollup config. | ai | |
| phantom-deps | phantom-dep:@live-change/dao-websocket | AI (phantom-deps): Same-org dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@live-change/image-frontend | AI (phantom-deps): Same-org dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:rollup-plugin-node-builtins | AI (phantom-deps): Build tool dep used in vite/rollup config. | ai | |
| phantom-deps | phantom-dep:vue3-scroll-border | AI (phantom-deps): UI plugin dep used in config/plugin registration. | ai | |
| phantom-deps | phantom-dep:wtfnode | AI (phantom-deps): Dev/debug tool referenced in scripts, not imported directly. | ai |
Versions (showing 34 of 134)
| Version | Deps | Published |
|---|---|---|
| 0.9.104 | 41 / 7 | |
| 0.9.103 | 41 / 7 | |
| 0.9.102 | 41 / 7 | |
| 0.9.101 | 41 / 7 | |
| 0.9.100 | 41 / 7 | |
| 0.9.99 | 41 / 7 | |
| 0.9.98 | 41 / 7 | |
| 0.9.97 | 41 / 7 | |
| 0.9.96 | 41 / 7 | |
| 0.9.95 | 41 / 7 | |
| 0.9.94 | 41 / 7 | |
| 0.9.93 | 41 / 7 | |
| 0.9.92 | 41 / 7 | |
| 0.9.91 | 41 / 7 | |
| 0.9.90 | 41 / 7 | |
| 0.9.89 | 41 / 7 | |
| 0.9.88 | 41 / 7 | |
| 0.9.87 | 41 / 7 | |
| 0.9.86 | 41 / 7 | |
| 0.9.85 | 41 / 7 | |
| 0.9.84 | 41 / 7 | |
| 0.9.83 | 41 / 7 | |
| 0.9.82 | 41 / 7 | |
| 0.9.81 | 41 / 7 | |
| 0.9.80 | 41 / 7 | |
| 0.9.79 | 41 / 7 | |
| 0.9.78 | 41 / 7 | |
| 0.9.77 | 41 / 7 | |
| 0.9.76 | 41 / 7 | |
| 0.9.75 | 41 / 7 | |
| 0.9.74 | 41 / 7 | |
| 0.9.73 | 41 / 7 | |
| 0.9.72 | 41 / 7 | |
| 0.9.71 | 41 / 7 |
v0.9.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.