@jx3box/jx3box-emotion
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:jquery | AI (phantom-deps): jQuery likely used as a peer/indirect dep in a Vue component; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@jx3box/jx3box-data | AI (phantom-deps): Same-org scoped dep; likely consumed indirectly through jx3box-common or config; stable FP for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.3.1 | 5 / 0 | |
| 1.3.0 | 5 / 0 | |
| 1.2.14 | 5 / 0 | |
| 1.2.13 | 5 / 0 | |
| 1.2.12 | 5 / 0 | |
| 1.2.11 | 5 / 0 | |
| 1.2.10 | 5 / 0 | |
| 1.2.9 | 5 / 0 |
v1.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.