← Home

@live-change/peer-connection-frontend

29
Versions
BSD-3-Clause
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

m8

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@live-change/vue3-components AI (phantom-deps): Same-org package; stable false positive for this monorepo component. ai
phantom-deps phantom-dep:@live-change/dao-websocket AI (phantom-deps): Same-org package; stable false positive for this monorepo component. ai
phantom-deps phantom-dep:@live-change/user-frontend AI (phantom-deps): Same-org package; stable false positive for this monorepo component. ai
phantom-deps phantom-dep:rollup-plugin-node-builtins AI (phantom-deps): Build tool referenced in config; stable false positive. ai
phantom-deps phantom-dep:boxicons AI (phantom-deps): Config-file reference in a frontend package; stable false positive for this package. ai
phantom-deps phantom-dep:cross-env AI (phantom-deps): Used in npm scripts, not imported; stable false positive. ai
phantom-deps phantom-dep:primeflex AI (phantom-deps): CSS framework referenced in config; stable false positive. ai
phantom-deps phantom-dep:primeicons AI (phantom-deps): Icon font referenced in config; stable false positive. ai
phantom-deps phantom-dep:compression AI (phantom-deps): Server middleware referenced in config; stable false positive. ai
phantom-deps phantom-dep:@vueuse/core AI (phantom-deps): Frontend utility referenced in config; stable false positive. ai
phantom-deps phantom-dep:serve-static AI (phantom-deps): Server middleware referenced in config; stable false positive. ai
phantom-deps phantom-dep:feather-icons AI (phantom-deps): Icon library referenced in config; stable false positive. ai
phantom-deps phantom-dep:@live-change/dao AI (phantom-deps): Same-org package; stable false positive for this monorepo component. ai
phantom-deps phantom-dep:v-shared-element AI (phantom-deps): Vue plugin referenced in config; stable false positive. ai
phantom-deps phantom-dep:codeceptjs-assert AI (phantom-deps): Test utility referenced in config; stable false positive. ai
phantom-deps phantom-dep:vue3-scroll-border AI (phantom-deps): Vue component referenced in config; stable false positive. ai
phantom-deps phantom-dep:serialize-javascript AI (phantom-deps): SSR utility referenced in config; stable false positive. ai
phantom-deps phantom-dep:@live-change/dao-vue3 AI (phantom-deps): Same-org package; stable false positive for this monorepo component. ai
phantom-deps phantom-dep:rollup-plugin-visualizer AI (phantom-deps): Build tool referenced in config; stable false positive. ai
npm-metadata no-description AI (npm-metadata): Stable pattern for this org's packages; not a spam indicator here. ai
provenance no-provenance AI (provenance): No provenance is consistent across all @live-change packages; not a risk signal for this org. ai
bogus-package bogus-package AI (bogus-package): Internal monorepo-style package; missing metadata is consistent across all @live-change packages. ai

Versions (showing 29 of 129)

Version Deps Published
0.9.99 30 / 7
0.9.98 30 / 7
0.9.97 30 / 7
0.9.96 30 / 7
0.9.95 30 / 7
0.9.94 30 / 7
0.9.93 30 / 7
0.9.92 30 / 7
0.9.91 30 / 7
0.9.90 30 / 7
0.9.89 30 / 7
0.9.88 30 / 7
0.9.87 30 / 7
0.9.86 30 / 7
0.9.85 30 / 7
0.9.84 30 / 7
0.9.83 30 / 7
0.9.82 30 / 7
0.9.81 30 / 7
0.9.80 30 / 7
0.9.79 30 / 7
0.9.78 30 / 7
0.9.77 30 / 7
0.9.76 30 / 7
0.9.75 30 / 7
0.9.74 30 / 7
0.9.73 30 / 7
0.9.72 30 / 7
0.9.71 30 / 7

v0.9.99

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.98

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.97

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.96

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.95

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.94

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.93

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.92

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.91

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.90

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.89

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.88

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.87

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.86

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.85

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.84

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.83

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.82

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.81

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.80

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.79

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.78

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.77

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.76

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.75

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.74

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.73

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.72

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.71

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.