@lumenflow/core
Core WU lifecycle tools 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:@lumenflow/packs-agent-runtime | AI (phantom-deps): Same-org scoped package; phantom-dep heuristic unreliable for monorepo barrel imports. | ai | |
| phantom-deps | phantom-dep:change-case | AI (phantom-deps): Likely re-exported via barrel; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:ms | AI (phantom-deps): ms is a declared runtime dep; likely used transitively or conditionally in this workflow framework. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @lumenflow/core is a workflow framework, not a typosquat of cors; name collision is coincidental. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type-only dep; not imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:cli-progress | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 5.8.15 | 26 / 5 | |
| 5.8.14 | 26 / 5 | |
| 5.8.13 | 26 / 5 | |
| 5.8.12 | 26 / 5 | |
| 5.8.11 | 26 / 5 | |
| 5.7.14 | 26 / 5 | |
| 5.4.0 | 26 / 5 | |
| 4.0.1 | 22 / 5 | |
| 4.0.0 | 22 / 5 | |
| 1.3.4 | 18 / 3 | |
| 1.3.3 | 18 / 3 | |
| 1.3.2 | 18 / 3 | |
| 1.3.0 | 17 / 3 | |
| 1.0.0 | 18 / 2 |
v5.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.14
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hellmai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hellmai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
2 findingsPackage name '@lumenflow/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
2 findingsPackage name '@lumenflow/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hellmai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.