@live-change/security-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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Established monorepo package; missing metadata is stable pattern, not spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal package with empty description; stable for this package. | ai | |
| phantom-deps | phantom-dep:serve-static | AI (phantom-deps): Config-file reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@live-change/dao | AI (phantom-deps): Same-org monorepo dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:compression | AI (phantom-deps): Config-file reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@live-change/dao-vue3 | AI (phantom-deps): Same-org monorepo dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:rollup-plugin-visualizer | AI (phantom-deps): Build config reference; stable false positive. | ai | |
| phantom-deps | phantom-dep:serialize-javascript | AI (phantom-deps): Config-file reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@vueuse/core | AI (phantom-deps): Config-file reference; stable false positive for this frontend package. | ai | |
| phantom-deps | phantom-dep:@live-change/user-service | AI (phantom-deps): Same-org dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@live-change/dao-websocket | AI (phantom-deps): Same-org dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@live-change/session-service | AI (phantom-deps): Same-org dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@live-change/vue3-components | AI (phantom-deps): Same-org dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@live-change/secret-code-service | AI (phantom-deps): Same-org dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:primevue | AI (phantom-deps): Frontend UI lib declared for config/build use; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@live-change/message-authentication-service | AI (phantom-deps): Same-org dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:luxon | AI (phantom-deps): Date lib declared for config/build; stable false positive. | ai | |
| phantom-deps | phantom-dep:cross-env | AI (phantom-deps): Used in npm scripts; stable false positive. | ai | |
| phantom-deps | phantom-dep:primeicons | AI (phantom-deps): Icon lib declared for config use; stable false positive. | ai | |
| phantom-deps | phantom-dep:vue-router | AI (phantom-deps): Frontend routing lib declared for config use; stable false positive. | ai | |
| phantom-deps | phantom-dep:@live-change/secret-link-service | AI (phantom-deps): Same-org dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:vue-meta | AI (phantom-deps): Declared for config/build use; stable false positive. | ai | |
| phantom-deps | phantom-dep:primeflex | AI (phantom-deps): CSS utility lib declared for config/build use; stable false positive. | ai | |
| phantom-deps | phantom-dep:get-port-sync | AI (phantom-deps): Dev/server tooling dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@live-change/cli | AI (phantom-deps): Same-org CLI tool used in scripts; stable false positive. | ai | |
| phantom-deps | phantom-dep:codeceptjs-assert | AI (phantom-deps): Test tooling dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:vue3-scroll-border | AI (phantom-deps): Frontend component declared for config use; stable false positive. | ai | |
| phantom-deps | phantom-dep:@live-change/vue3-ssr | AI (phantom-deps): Same-org dep used in build config; stable false positive. | ai | |
| phantom-deps | phantom-dep:@live-change/framework | AI (phantom-deps): Same-org dep; stable false positive. | ai |
Versions (showing 51 of 134)
| Version | Deps | Published |
|---|---|---|
| 0.9.209 | 28 / 8 | |
| 0.9.208 | 28 / 8 | |
| 0.9.207 | 28 / 8 | |
| 0.9.206 | 28 / 8 | |
| 0.9.205 | 28 / 8 | |
| 0.9.204 | 28 / 8 | |
| 0.9.203 | 28 / 8 | |
| 0.9.201 | 28 / 8 | |
| 0.9.200 | 28 / 8 | |
| 0.9.199 | 28 / 8 | |
| 0.9.198 | 28 / 8 | |
| 0.9.197 | 28 / 8 | |
| 0.9.196 | 28 / 8 | |
| 0.9.195 | 28 / 8 | |
| 0.9.194 | 28 / 8 | |
| 0.9.193 | 28 / 8 | |
| 0.9.192 | 28 / 8 | |
| 0.9.191 | 28 / 8 | |
| 0.9.190 | 28 / 8 | |
| 0.9.189 | 28 / 8 | |
| 0.9.188 | 28 / 8 | |
| 0.9.187 | 28 / 8 | |
| 0.9.186 | 28 / 8 | |
| 0.9.185 | 28 / 8 | |
| 0.9.184 | 28 / 8 | |
| 0.9.183 | 28 / 8 | |
| 0.9.182 | 28 / 8 | |
| 0.9.181 | 28 / 8 | |
| 0.9.180 | 28 / 8 | |
| 0.9.179 | 28 / 8 | |
| 0.9.177 | 28 / 8 | |
| 0.9.176 | 28 / 8 | |
| 0.9.175 | 28 / 8 | |
| 0.9.174 | 28 / 8 | |
| 0.9.173 | 28 / 8 | |
| 0.9.171 | 28 / 8 | |
| 0.9.169 | 28 / 8 | |
| 0.9.167 | 28 / 8 | |
| 0.9.166 | 28 / 8 | |
| 0.9.165 | 28 / 8 | |
| 0.9.164 | 28 / 8 | |
| 0.9.163 | 28 / 8 | |
| 0.9.162 | 28 / 8 | |
| 0.9.161 | 28 / 8 | |
| 0.9.160 | 28 / 8 | |
| 0.9.159 | 28 / 8 | |
| 0.9.158 | 28 / 8 | |
| 0.9.157 | 28 / 8 | |
| 0.9.156 | 28 / 8 | |
| 0.9.155 | 28 / 8 | |
| 0.9.154 | 28 / 8 |
v0.9.209
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.208
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.207
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.206
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.205
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.203
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.201
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.200
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.199
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.198
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.197
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.196
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.195
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.194
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.193
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.192
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.191
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.190
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.189
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.188
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.187
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.186
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.185
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.184
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.183
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.182
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.181
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.180
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.179
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.177
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.176
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.175
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.174
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.173
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.171
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.169
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.167
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.166
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.165
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.164
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.163
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.162
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.161
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.160
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.159
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.158
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.157
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.156
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.155
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.154
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.