@live-change/server
Live Change Framework - 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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:semver | AI (typosquat): Scoped monorepo package @live-change/server; Levenshtein match to 'semver' is a false positive with no brand confusion. | ai | |
| phantom-deps | phantom-dep:yargs | AI (phantom-deps): CLI tool dep referenced in config/scripts; stable false positive for this server package. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Config-referenced dep; stable false positive for this server package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/api | AI (phantom-deps): Telemetry dep referenced in config; stable false positive for this server package. | ai | |
| phantom-deps | phantom-dep:http-proxy-middleware | AI (phantom-deps): Proxy dep referenced in config; stable false positive for this server package. | ai | |
| phantom-deps | phantom-dep:@live-change/dao-sockjs | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for ESM monorepo packages. | ai |
Versions (showing 34 of 134)
| Version | Deps | Published |
|---|---|---|
| 0.9.104 | 16 / 0 | |
| 0.9.103 | 16 / 0 | |
| 0.9.102 | 16 / 0 | |
| 0.9.101 | 16 / 0 | |
| 0.9.100 | 16 / 0 | |
| 0.9.99 | 16 / 0 | |
| 0.9.98 | 16 / 0 | |
| 0.9.97 | 16 / 0 | |
| 0.9.96 | 16 / 0 | |
| 0.9.95 | 16 / 0 | |
| 0.9.94 | 16 / 0 | |
| 0.9.93 | 16 / 0 | |
| 0.9.92 | 16 / 0 | |
| 0.9.91 | 16 / 0 | |
| 0.9.90 | 16 / 0 | |
| 0.9.89 | 16 / 0 | |
| 0.9.88 | 16 / 0 | |
| 0.9.87 | 16 / 0 | |
| 0.9.86 | 16 / 0 | |
| 0.9.85 | 16 / 0 | |
| 0.9.84 | 16 / 0 | |
| 0.9.83 | 16 / 0 | |
| 0.9.82 | 16 / 0 | |
| 0.9.81 | 16 / 0 | |
| 0.9.80 | 16 / 0 | |
| 0.9.79 | 16 / 0 | |
| 0.9.78 | 16 / 0 | |
| 0.9.77 | 16 / 0 | |
| 0.9.76 | 16 / 0 | |
| 0.9.75 | 16 / 0 | |
| 0.9.74 | 16 / 0 | |
| 0.9.73 | 16 / 0 | |
| 0.9.72 | 16 / 0 | |
| 0.9.71 | 16 / 0 |
v0.9.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.