@jaypie/core
Supply chain provenance
Status for the latest visible version.
Maintainers
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 @jaypie/core package; no relation to cors. Levenshtein match is coincidental. | ai | |
| dependencies | unvetted-dep:@jaypie/kit | AI (dependencies): Internal @jaypie namespace dependency from same publisher. | ai | |
| dependencies | unvetted-dep:@jaypie/logger | AI (dependencies): Internal @jaypie namespace dependency from same publisher. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.2.2 | 3 / 3 | |
| 1.2.0 | 3 / 3 | |
| 1.1.19 | 3 / 0 | |
| 1.1.18 | 3 / 0 | |
| 1.1.17 | 3 / 0 | |
| 1.1.15 | 2 / 0 | |
| 1.1.14 | 2 / 0 | |
| 1.1.13 | 2 / 0 | |
| 1.1.12 | 2 / 0 | |
| 1.1.11 | 2 / 0 | |
| 1.1.10 | 2 / 0 | |
| 1.1.9 | 2 / 0 | |
| 1.1.8 | 2 / 0 | |
| 1.1.7 | 2 / 0 | |
| 1.1.6 | 3 / 0 |
v1.2.2
2 findingsPackage name '@jaypie/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0
2 findingsPackage name '@jaypie/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.19
2 findingsPackage name '@jaypie/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.18
2 findingsPackage name '@jaypie/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.17
2 findingsPackage name '@jaypie/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.15
2 findingsPackage name '@jaypie/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.14
2 findingsPackage name '@jaypie/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.13
2 findingsPackage name '@jaypie/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.12
2 findingsPackage name '@jaypie/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.11
2 findingsPackage name '@jaypie/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
2 findingsPackage name '@jaypie/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
2 findingsPackage name '@jaypie/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
2 findingsPackage name '@jaypie/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
2 findingsPackage name '@jaypie/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
2 findingsPackage name '@jaypie/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.