@lumenflow/cli
Command-line interface for LumenFlow workflow framework
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:simple-statistics | AI (phantom-deps): Monorepo config-file references; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Monorepo config-file references; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:glob | AI (phantom-deps): Monorepo config-file references; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:p-retry | AI (phantom-deps): Monorepo config-file references; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ps-list | AI (phantom-deps): Monorepo config-file references; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Monorepo config-file references; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tiktoken | AI (phantom-deps): Monorepo config-file references; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:micromatch | AI (phantom-deps): Monorepo config-file references; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:picocolors | AI (phantom-deps): Monorepo config-file references; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:change-case | AI (phantom-deps): Monorepo config-file references; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:gray-matter | AI (phantom-deps): Monorepo config-file references; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:cli-progress | AI (phantom-deps): Monorepo config-file references; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @lumenflow/cli is a distinct workflow CLI; Levenshtein match to 'joi' is coincidental and not a typosquat. | ai |
Versions (showing 51 of 151)
| Version | Deps | Published |
|---|---|---|
| 5.8.3 | 34 / 5 | |
| 5.8.0 | 34 / 5 | |
| 5.7.24 | 34 / 5 | |
| 5.7.23 | 34 / 5 | |
| 5.7.22 | 34 / 5 | |
| 5.7.21 | 34 / 5 | |
| 5.7.18 | 34 / 5 | |
| 5.7.17 | 34 / 5 | |
| 5.7.16 | 34 / 5 | |
| 5.7.14 | 34 / 5 | |
| 5.7.12 | 34 / 5 | |
| 5.5.0 | 34 / 5 | |
| 5.4.0 | 34 / 5 | |
| 5.3.2 | 34 / 5 | |
| 4.23.0 | 31 / 5 | |
| 4.22.0 | 31 / 5 | |
| 4.21.0 | 31 / 5 | |
| 4.19.1 | 31 / 5 | |
| 4.19.0 | 31 / 5 | |
| 4.18.0 | 31 / 5 | |
| 4.17.0 | 31 / 5 | |
| 4.16.0 | 31 / 5 | |
| 4.15.0 | 31 / 5 | |
| 4.14.0 | 31 / 5 | |
| 4.13.0 | 31 / 5 | |
| 4.12.4 | 31 / 5 | |
| 4.12.2 | 31 / 5 | |
| 4.12.1 | 31 / 5 | |
| 4.12.0 | 31 / 5 | |
| 4.11.0 | 31 / 5 | |
| 4.10.0 | 31 / 5 | |
| 4.1.0 | 31 / 5 | |
| 3.21.0 | 31 / 5 | |
| 3.20.0 | 31 / 5 | |
| 3.19.0 | 31 / 5 | |
| 3.18.0 | 31 / 5 | |
| 3.17.7 | 31 / 5 | |
| 3.17.6 | 31 / 5 | |
| 3.17.5 | 31 / 5 | |
| 3.17.4 | 31 / 5 | |
| 3.17.3 | 31 / 5 | |
| 3.17.2 | 31 / 5 | |
| 3.17.1 | 31 / 5 | |
| 3.17.0 | 31 / 5 | |
| 3.16.1 | 31 / 5 | |
| 3.14.0 | 31 / 5 | |
| 3.13.2 | 31 / 5 | |
| 3.13.1 | 31 / 5 | |
| 3.13.0 | 31 / 5 | |
| 3.12.11 | 31 / 5 | |
| 3.12.10 | 31 / 5 |
v5.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.