@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 13 of 113)
| Version | Deps | Published |
|---|---|---|
| 1.2.7 | 9 / 38 | |
| 1.2.6 | 8 / 38 | |
| 1.2.5 | 8 / 38 | |
| 1.2.4 | 8 / 38 | |
| 1.2.3 | 8 / 38 | |
| 1.2.2 | 8 / 38 | |
| 1.2.1 | 8 / 38 | |
| 1.2.0 | 8 / 38 | |
| 1.0.4 | 7 / 36 | |
| 1.0.3 | 7 / 36 | |
| 1.0.2 | 7 / 36 | |
| 1.0.1 | 0 / 0 | |
| 1.0.0 | 0 / 0 |
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.2
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.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.