@jx3box/jx3box-talent
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package; no provenance is consistent across all versions and poses no active risk. | ai | |
| phantom-deps | phantom-dep:progress | AI (phantom-deps): progress is a CLI progress-bar used in build tools, consistent with config-file-only reference. | ai | |
| phantom-deps | phantom-dep:cli-color | AI (phantom-deps): CLI utility used in build scripts, not expected to be directly imported in library source. | ai | |
| phantom-deps | phantom-dep:papaparse | AI (phantom-deps): CSV parsing used in build/data tools; config-file reference is plausible. | ai | |
| phantom-deps | phantom-dep:moment | AI (phantom-deps): CLI/build tooling package; moment likely used in build scripts, not direct source imports. | ai | |
| phantom-deps | phantom-dep:@jx3box/jx3box-data | AI (phantom-deps): Same-org dependency; phantom-dep heuristic unreliable for org-scoped packages. | ai | |
| phantom-deps | phantom-dep:@jx3box/jx3box-build-common | AI (phantom-deps): Same-org build tooling; phantom-dep heuristic unreliable for org-scoped build packages. | ai | |
| phantom-deps | phantom-dep:ansi-escapes | AI (phantom-deps): Terminal utility for build scripts; consistent with config-only reference pattern. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.3.14 | 10 / 10 | |
| 1.3.13 | 10 / 10 | |
| 1.3.12 | 10 / 10 | |
| 1.3.11 | 10 / 10 | |
| 1.3.10 | 10 / 10 | |
| 1.3.9 | 10 / 10 | |
| 1.3.8 | 10 / 10 | |
| 1.3.7 | 10 / 10 | |
| 1.3.6 | 10 / 10 | |
| 1.3.5 | 10 / 10 | |
| 1.3.4 | 10 / 10 |
v1.3.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.