@player-ui/reference-assets-plugin-react
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Large monorepo with frequent releases; publish env change is plausible and no other risk signals present. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across this package's history; no malware indicators to elevate concern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing metadata is typical for this org's packages, not a spam/malware signal. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known implicit runtime dep for TypeScript compiled packages; stable false positive. | ai | |
| phantom-deps | phantom-dep:@player-ui/partial-match-registry | AI (phantom-deps): Same-org dep used transitively; phantom-dep heuristic fires but this is a stable false positive for this monorepo package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.0.1 | 12 / 1 | |
| 1.0.0 | 12 / 1 | |
| 0.15.5 | 12 / 1 | |
| 0.15.4 | 12 / 1 | |
| 0.15.3 | 12 / 1 | |
| 0.15.2 | 12 / 1 | |
| 0.15.1 | 12 / 1 | |
| 0.15.0 | 12 / 1 | |
| 0.14.1 | 12 / 1 | |
| 0.14.0 | 12 / 1 | |
| 0.13.0 | 12 / 1 | |
| 0.12.0 | 13 / 1 | |
| 0.11.2 | 13 / 1 | |
| 0.11.1 | 13 / 1 | |
| 0.11.0 | 13 / 1 | |
| 0.10.4 | 13 / 1 | |
| 0.10.3 | 12 / 1 | |
| 0.10.2 | 12 / 1 | |
| 0.10.1 | 12 / 1 | |
| 0.10.0 | 12 / 1 | |
| 0.9.1 | 12 / 1 | |
| 0.8.0 | 12 / 1 | |
| 0.7.3 | 8 / 0 |
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.