@journeyapps-labs/lib-reactor-data-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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Internal scoped library from established org; missing description is cosmetic, not a risk indicator. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@journeyapps-labs/lib-reactor-utils | AI (phantom-deps): Same-org scoped dep; likely used transitively or in compiled output rather than direct import. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.11 | 5 / 2 | |
| 1.0.7 | 5 / 2 | |
| 1.0.6 | 5 / 2 | |
| 1.0.3 | 5 / 2 | |
| 1.0.1 | 5 / 2 |
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.