jaypie
The main entrypoint for Jaypie packages
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Umbrella re-export package; thin README and no keywords are expected for this type of package. | ai | |
| phantom-deps | phantom-dep:@jaypie/core | AI (phantom-deps): @jaypie/core is a sibling dep re-exported via the umbrella; not directly imported in source is expected. | ai |
Versions (showing 100 of 175)
| Version | Deps | Published |
|---|---|---|
| 1.2.71 | 8 / 10 | |
| 1.2.70 | 8 / 10 | |
| 1.2.69 | 8 / 10 | |
| 1.2.68 | 8 / 10 | |
| 1.2.67 | 8 / 10 | |
| 1.2.66 | 8 / 10 | |
| 1.2.65 | 8 / 10 | |
| 1.2.64 | 8 / 10 | |
| 1.2.63 | 8 / 10 | |
| 1.2.62 | 8 / 10 | |
| 1.2.61 | 8 / 10 | |
| 1.2.60 | 8 / 10 | |
| 1.2.59 | 8 / 10 | |
| 1.2.58 | 8 / 10 | |
| 1.2.57 | 8 / 10 | |
| 1.2.56 | 8 / 10 | |
| 1.2.55 | 8 / 10 | |
| 1.2.54 | 8 / 9 | |
| 1.2.53 | 8 / 9 | |
| 1.2.52 | 8 / 9 | |
| 1.2.51 | 8 / 9 | |
| 1.2.50 | 8 / 10 | |
| 1.2.49 | 8 / 10 | |
| 1.2.48 | 8 / 10 | |
| 1.2.47 | 8 / 10 | |
| 1.2.46 | 8 / 10 | |
| 1.2.45 | 8 / 10 | |
| 1.2.44 | 8 / 10 | |
| 1.2.43 | 8 / 10 | |
| 1.2.42 | 8 / 10 | |
| 1.2.41 | 8 / 10 | |
| 1.2.40 | 8 / 10 | |
| 1.2.39 | 8 / 10 | |
| 1.2.38 | 8 / 10 | |
| 1.2.37 | 8 / 10 | |
| 1.2.36 | 8 / 10 | |
| 1.2.35 | 8 / 10 | |
| 1.2.34 | 8 / 10 | |
| 1.2.33 | 8 / 10 | |
| 1.2.32 | 8 / 10 | |
| 1.2.31 | 8 / 10 | |
| 1.2.30 | 8 / 10 | |
| 1.2.29 | 8 / 10 | |
| 1.2.28 | 8 / 10 | |
| 1.2.27 | 8 / 10 | |
| 1.2.26 | 8 / 10 | |
| 1.2.25 | 8 / 10 | |
| 1.2.24 | 8 / 10 | |
| 1.2.23 | 8 / 10 | |
| 1.2.22 | 8 / 10 | |
| 1.2.21 | 8 / 10 | |
| 1.2.20 | 8 / 10 | |
| 1.2.19 | 8 / 10 | |
| 1.2.18 | 8 / 10 | |
| 1.2.17 | 8 / 10 | |
| 1.2.16 | 8 / 10 | |
| 1.2.15 | 8 / 10 | |
| 1.2.14 | 8 / 10 | |
| 1.2.13 | 8 / 10 | |
| 1.2.12 | 8 / 10 | |
| 1.2.11 | 8 / 10 | |
| 1.2.10 | 8 / 10 | |
| 1.2.9 | 8 / 10 | |
| 1.2.8 | 8 / 10 | |
| 1.2.7 | 8 / 10 | |
| 1.2.6 | 8 / 10 | |
| 1.2.5 | 8 / 10 | |
| 1.2.4 | 8 / 10 | |
| 1.2.3 | 8 / 10 | |
| 1.2.2 | 8 / 10 | |
| 1.2.1 | 8 / 10 | |
| 1.2.0 | 8 / 10 | |
| 1.1.77 | 8 / 10 | |
| 1.1.76 | 8 / 10 | |
| 1.1.75 | 8 / 10 | |
| 1.1.74 | 8 / 10 | |
| 1.1.73 | 8 / 10 | |
| 1.1.72 | 8 / 10 | |
| 1.1.71 | 8 / 10 | |
| 1.1.70 | 8 / 0 | |
| 1.1.69 | 8 / 0 | |
| 1.1.68 | 7 / 0 | |
| 1.1.66 | 7 / 0 | |
| 1.1.65 | 7 / 0 | |
| 1.1.64 | 7 / 0 | |
| 1.1.63 | 7 / 0 | |
| 1.1.62 | 7 / 0 | |
| 1.1.61 | 7 / 0 | |
| 1.1.60 | 7 / 0 | |
| 1.1.59 | 7 / 0 | |
| 1.1.58 | 7 / 0 | |
| 1.1.57 | 7 / 0 | |
| 1.1.56 | 7 / 0 | |
| 1.1.55 | 7 / 0 | |
| 1.1.54 | 7 / 0 | |
| 1.1.53 | 7 / 0 | |
| 1.1.52 | 7 / 0 | |
| 1.1.51 | 7 / 0 | |
| 1.1.50 | 7 / 0 | |
| 1.1.49 | 7 / 0 |
v1.2.71
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.70
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.69
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.68
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.67
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.66
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.65
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.64
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.63
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.62
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.61
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.60
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.59
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.58
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.77
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.76
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.75
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.74
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.73
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.