@node-in-layers/core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @node-in-layers/core is a framework core library, not a typosquat of cors; name collision is coincidental. | ai | |
| phantom-deps | phantom-dep:loglevel | AI (phantom-deps): loglevel is a declared runtime dep; phantom-dep heuristic fires on indirect usage patterns common in framework code. | ai | |
| phantom-deps | phantom-dep:modern-async | AI (phantom-deps): modern-async is a declared runtime dep; phantom-dep heuristic fires on indirect usage patterns common in framework code. | ai |
Versions (showing 100 of 113)
| Version | Deps | Published |
|---|---|---|
| 1.17.1 | 10 / 44 | |
| 1.17.0 | 10 / 43 | |
| 1.16.0 | 10 / 43 | |
| 1.15.18 | 10 / 43 | |
| 1.15.16 | 10 / 43 | |
| 1.15.15 | 10 / 43 | |
| 1.15.13 | 10 / 43 | |
| 1.15.12 | 10 / 43 | |
| 1.15.11 | 10 / 43 | |
| 1.15.10 | 10 / 43 | |
| 1.15.9 | 10 / 43 | |
| 1.15.8 | 10 / 43 | |
| 1.15.7 | 10 / 43 | |
| 1.15.6 | 10 / 43 | |
| 1.15.5 | 9 / 43 | |
| 1.15.4 | 9 / 43 | |
| 1.15.3 | 9 / 43 | |
| 1.15.2 | 9 / 43 | |
| 1.15.1 | 9 / 43 | |
| 1.15.0 | 9 / 43 | |
| 1.14.0 | 9 / 43 | |
| 1.13.5 | 9 / 43 | |
| 1.13.4 | 9 / 43 | |
| 1.13.3 | 9 / 43 | |
| 1.13.2 | 9 / 43 | |
| 1.13.1 | 9 / 43 | |
| 1.13.0 | 9 / 43 | |
| 1.12.8 | 11 / 39 | |
| 1.12.7 | 11 / 39 | |
| 1.12.6 | 11 / 39 | |
| 1.12.5 | 11 / 39 | |
| 1.12.4 | 11 / 39 | |
| 1.12.3 | 11 / 39 | |
| 1.12.2 | 11 / 39 | |
| 1.12.1 | 11 / 39 | |
| 1.11.2 | 11 / 39 | |
| 1.11.1 | 11 / 39 | |
| 1.11.0 | 11 / 39 | |
| 1.10.16 | 11 / 39 | |
| 1.10.15 | 11 / 39 | |
| 1.10.14 | 11 / 39 | |
| 1.10.13 | 11 / 39 | |
| 1.10.12 | 11 / 39 | |
| 1.10.11 | 11 / 39 | |
| 1.10.10 | 11 / 39 | |
| 1.10.9 | 11 / 39 | |
| 1.10.8 | 11 / 39 | |
| 1.10.7 | 11 / 39 | |
| 1.10.6 | 11 / 38 | |
| 1.10.5 | 11 / 38 | |
| 1.10.4 | 11 / 38 | |
| 1.10.3 | 11 / 38 | |
| 1.10.2 | 11 / 38 | |
| 1.10.1 | 11 / 38 | |
| 1.10.0 | 11 / 38 | |
| 1.9.1 | 11 / 38 | |
| 1.9.0 | 11 / 38 | |
| 1.8.3 | 10 / 38 | |
| 1.8.2 | 10 / 38 | |
| 1.8.1 | 10 / 38 | |
| 1.8.0 | 10 / 38 | |
| 1.7.0 | 10 / 38 | |
| 1.6.8 | 10 / 38 | |
| 1.6.7 | 10 / 38 | |
| 1.6.6 | 10 / 38 | |
| 1.6.5 | 10 / 38 | |
| 1.6.4 | 10 / 38 | |
| 1.6.3 | 10 / 38 | |
| 1.6.2 | 10 / 38 | |
| 1.6.1 | 10 / 38 | |
| 1.6.0 | 10 / 38 | |
| 1.5.9 | 10 / 38 | |
| 1.5.8 | 10 / 38 | |
| 1.5.7 | 10 / 38 | |
| 1.5.6 | 10 / 38 | |
| 1.5.5 | 10 / 38 | |
| 1.5.4 | 10 / 38 | |
| 1.5.3 | 10 / 38 | |
| 1.5.2 | 10 / 38 | |
| 1.5.1 | 10 / 38 | |
| 1.5.0 | 10 / 38 | |
| 1.4.3 | 9 / 38 | |
| 1.4.2 | 9 / 38 | |
| 1.4.1 | 9 / 38 | |
| 1.4.0 | 9 / 38 | |
| 1.3.7 | 9 / 38 | |
| 1.3.6 | 9 / 38 | |
| 1.3.5 | 9 / 38 | |
| 1.3.4 | 9 / 38 | |
| 1.3.3 | 9 / 38 | |
| 1.3.2 | 9 / 38 | |
| 1.3.1 | 9 / 38 | |
| 1.3.0 | 9 / 38 | |
| 1.2.14 | 9 / 38 | |
| 1.2.13 | 9 / 38 | |
| 1.2.12 | 9 / 38 | |
| 1.2.11 | 9 / 38 | |
| 1.2.10 | 9 / 38 | |
| 1.2.9 | 9 / 38 | |
| 1.2.8 | 9 / 38 |
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
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.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
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.7
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.1
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.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.