@node-in-layers/tasks
A Node In Layers Package for creating and running Asynchronous Tasks and Workflows.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:modern-async | AI (dependencies): Legitimate async utility; no malware indicators, stable dependency across versions. | ai | |
| dependencies | unvetted-dep:functional-models | AI (dependencies): Functional modeling library; no malware indicators, consistent usage across versions. | ai | |
| dependencies | unvetted-dep:@node-in-layers/core | AI (dependencies): Same org/ecosystem package; no malware indicators, expected core dependency. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present for this package. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a declared runtime dep; phantom-dep fires due to indirect usage pattern in this framework-style package. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): axios is a declared runtime dep; phantom-dep fires due to indirect usage pattern in this framework-style package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 8 / 39 | |
| 1.1.0 | 8 / 39 | |
| 1.0.7 | 8 / 39 | |
| 1.0.6 | 8 / 39 | |
| 1.0.5 | 8 / 39 | |
| 1.0.4 | 8 / 39 | |
| 1.0.3 | 8 / 39 | |
| 1.0.2 | 8 / 39 | |
| 1.0.1 | 8 / 39 | |
| 1.0.0 | 2 / 38 |
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.