@live-change/cli
Live Change Framework - command line interface
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:joi | AI (typosquat): Scoped package @live-change/cli vs 'joi' is a spurious Levenshtein match; no brand impersonation. | ai | |
| phantom-deps | phantom-dep:sockjs | AI (phantom-deps): sockjs is a runtime dep passed through to server-side code; phantom-dep heuristic fires on CLI tools that load deps dynamically. | ai | |
| phantom-deps | phantom-dep:resolve | AI (phantom-deps): resolve used as a utility in CLI tooling; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:websocket | AI (phantom-deps): websocket is a runtime transport dep; phantom-dep heuristic is unreliable for CLI wrappers. | ai | |
| phantom-deps | phantom-dep:serialize-javascript | AI (phantom-deps): Stable false positive for this CLI package; dep used indirectly via framework. | ai | |
| phantom-deps | phantom-dep:@live-change/db-server | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic unreliable for CLI orchestration packages. | ai | |
| phantom-deps | phantom-dep:@live-change/dao-sockjs | AI (phantom-deps): Same-org monorepo dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@live-change/dao-websocket | AI (phantom-deps): Same-org monorepo dep; stable false positive. | ai |
Versions (showing 34 of 134)
| Version | Deps | Published |
|---|---|---|
| 0.9.104 | 14 / 0 | |
| 0.9.103 | 14 / 0 | |
| 0.9.102 | 14 / 0 | |
| 0.9.101 | 14 / 0 | |
| 0.9.100 | 14 / 0 | |
| 0.9.99 | 14 / 0 | |
| 0.9.98 | 14 / 0 | |
| 0.9.97 | 14 / 0 | |
| 0.9.96 | 14 / 0 | |
| 0.9.95 | 14 / 0 | |
| 0.9.94 | 14 / 0 | |
| 0.9.93 | 14 / 0 | |
| 0.9.92 | 14 / 0 | |
| 0.9.91 | 14 / 0 | |
| 0.9.90 | 14 / 0 | |
| 0.9.89 | 14 / 0 | |
| 0.9.88 | 14 / 0 | |
| 0.9.87 | 14 / 0 | |
| 0.9.86 | 14 / 0 | |
| 0.9.85 | 14 / 0 | |
| 0.9.84 | 14 / 0 | |
| 0.9.83 | 14 / 0 | |
| 0.9.82 | 14 / 0 | |
| 0.9.81 | 14 / 0 | |
| 0.9.80 | 14 / 0 | |
| 0.9.79 | 14 / 0 | |
| 0.9.78 | 14 / 0 | |
| 0.9.77 | 14 / 0 | |
| 0.9.76 | 14 / 0 | |
| 0.9.75 | 14 / 0 | |
| 0.9.74 | 14 / 0 | |
| 0.9.73 | 14 / 0 | |
| 0.9.72 | 14 / 0 | |
| 0.9.71 | 14 / 0 |
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. Consider requesting the maintainer enable provenance via CI/CD.
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. 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.