@lumenflow/host
Generic runtime primitives for LumenFlow (ADR-012 host layer)
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped package @lumenflow/host; levenshtein match to 'jest' is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped package @lumenflow/host; levenshtein match to 'got' is coincidental, not impersonation. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 5.10.8 | 4 / 4 | |
| 5.8.15 | 4 / 4 | |
| 5.8.14 | 4 / 4 | |
| 5.8.13 | 4 / 4 | |
| 5.8.12 | 4 / 4 | |
| 5.8.11 | 4 / 4 | |
| 5.8.3 | 4 / 4 | |
| 5.8.0 | 4 / 4 | |
| 5.7.24 | 4 / 4 | |
| 5.7.23 | 4 / 4 | |
| 5.7.22 | 4 / 4 | |
| 5.7.21 | 4 / 4 | |
| 5.7.18 | 4 / 4 | |
| 5.7.17 | 4 / 4 | |
| 5.7.16 | 4 / 4 | |
| 5.7.14 | 4 / 4 | |
| 5.7.12 | 4 / 4 | |
| 5.5.0 | 4 / 4 | |
| 5.4.0 | 4 / 4 | |
| 5.3.2 | 4 / 4 | |
| 5.3.1 | 4 / 4 | |
| 5.3.0 | 4 / 4 | |
| 5.2.10 | 4 / 4 | |
| 5.2.9 | 4 / 4 | |
| 5.2.8 | 4 / 4 | |
| 5.2.7 | 4 / 4 | |
| 5.2.6 | 4 / 4 | |
| 5.2.5 | 4 / 4 | |
| 5.2.4 | 4 / 4 | |
| 5.2.3 | 4 / 4 | |
| 5.2.2 | 4 / 4 | |
| 5.2.1 | 4 / 4 | |
| 5.2.0 | 4 / 4 | |
| 5.1.0 | 4 / 4 | |
| 5.0.3 | 4 / 4 | |
| 5.0.2 | 4 / 4 |
v5.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.