@jaypie/express
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): Monorepo package with 109 published versions; sparse README/keywords is a style choice, not spam. | ai |
Versions (showing 61 of 61)
| Version | Deps | Published |
|---|---|---|
| 1.2.29 | 3 / 7 | |
| 1.2.28 | 3 / 7 | |
| 1.2.27 | 3 / 7 | |
| 1.2.26 | 3 / 7 | |
| 1.2.25 | 3 / 6 | |
| 1.2.24 | 3 / 6 | |
| 1.2.23 | 3 / 6 | |
| 1.2.22 | 3 / 6 | |
| 1.2.21 | 3 / 6 | |
| 1.2.20 | 3 / 6 | |
| 1.2.19 | 3 / 6 | |
| 1.2.18 | 3 / 6 | |
| 1.2.17 | 3 / 6 | |
| 1.2.16 | 3 / 6 | |
| 1.2.15 | 3 / 6 | |
| 1.2.14 | 3 / 6 | |
| 1.2.13 | 3 / 6 | |
| 1.2.12 | 3 / 6 | |
| 1.2.11 | 3 / 6 | |
| 1.2.10 | 3 / 6 | |
| 1.2.9 | 3 / 6 | |
| 1.2.8 | 3 / 6 | |
| 1.2.7 | 3 / 6 | |
| 1.2.6 | 3 / 6 | |
| 1.2.5 | 3 / 6 | |
| 1.2.4 | 3 / 6 | |
| 1.2.3 | 4 / 6 | |
| 1.1.17 | 5 / 1 | |
| 1.1.16 | 5 / 1 | |
| 1.1.15 | 5 / 1 | |
| 1.1.14 | 5 / 1 | |
| 1.1.13 | 5 / 1 | |
| 1.1.12 | 4 / 1 | |
| 1.1.11 | 4 / 0 | |
| 1.1.10 | 4 / 0 | |
| 1.1.9 | 4 / 0 | |
| 1.1.8 | 4 / 0 | |
| 1.1.7 | 4 / 0 | |
| 1.1.6 | 4 / 0 | |
| 1.1.5 | 4 / 0 | |
| 1.1.4 | 4 / 0 | |
| 1.1.3 | 4 / 0 | |
| 1.1.2 | 4 / 0 | |
| 1.1.1 | 4 / 0 | |
| 1.1.0 | 2 / 0 | |
| 1.0.15 | 2 / 15 | |
| 1.0.14 | 2 / 15 | |
| 1.0.13 | 2 / 15 | |
| 1.0.12 | 2 / 15 | |
| 1.0.11 | 2 / 15 | |
| 1.0.10 | 2 / 15 | |
| 1.0.9 | 2 / 15 | |
| 1.0.8 | 2 / 15 | |
| 1.0.7 | 2 / 15 | |
| 1.0.6 | 2 / 15 | |
| 1.0.5 | 5 / 12 | |
| 1.0.4 | 4 / 16 | |
| 1.0.3 | 4 / 16 | |
| 1.0.2 | 4 / 16 | |
| 1.0.1 | 4 / 16 | |
| 1.0.0 | 4 / 16 |
v1.2.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.