@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 |
|---|---|---|
| 3.1.2 | 30 / 5 | |
| 3.1.1 | 30 / 5 | |
| 3.1.0 | 30 / 5 | |
| 3.0.0 | 17 / 4 | |
| 2.21.1 | 16 / 4 | |
| 2.21.0 | 16 / 4 | |
| 2.20.1 | 16 / 4 | |
| 2.20.0 | 16 / 4 | |
| 2.19.0 | 16 / 4 | |
| 2.18.3 | 15 / 3 | |
| 2.18.2 | 15 / 3 | |
| 2.18.1 | 15 / 3 | |
| 2.18.0 | 15 / 3 | |
| 2.17.0 | 15 / 3 | |
| 2.16.0 | 15 / 3 | |
| 2.15.2 | 14 / 3 | |
| 2.15.1 | 14 / 3 | |
| 2.15.0 | 14 / 3 | |
| 2.14.1 | 14 / 3 | |
| 2.14.0 | 14 / 3 | |
| 2.13.0 | 14 / 3 | |
| 2.12.0 | 14 / 3 | |
| 2.11.0 | 14 / 3 | |
| 2.10.0 | 14 / 3 | |
| 2.9.0 | 14 / 3 | |
| 2.8.0 | 14 / 3 | |
| 2.7.0 | 14 / 3 | |
| 2.6.0 | 14 / 3 | |
| 2.5.1 | 14 / 3 | |
| 2.5.0 | 14 / 3 | |
| 2.4.0 | 14 / 3 | |
| 2.3.2 | 14 / 3 | |
| 2.3.1 | 14 / 3 | |
| 2.2.2 | 14 / 3 | |
| 2.2.1 | 14 / 3 | |
| 2.2.0 | 14 / 3 | |
| 2.1.2 | 14 / 3 | |
| 2.1.1 | 14 / 3 | |
| 2.1.0 | 14 / 3 | |
| 2.0.0 | 14 / 3 | |
| 1.6.0 | 14 / 3 | |
| 1.5.0 | 14 / 3 | |
| 1.4.0 | 14 / 3 | |
| 1.3.6 | 14 / 3 | |
| 1.3.5 | 14 / 3 | |
| 1.3.4 | 14 / 3 | |
| 1.3.3 | 14 / 3 | |
| 1.3.2 | 14 / 3 | |
| 1.3.0 | 14 / 3 | |
| 1.1.0 | 15 / 2 | |
| 1.0.0 | 10 / 2 |
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.