@player-ui/async-node-plugin
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 | no-provenance | AI (provenance): Provenance gap is a CI/CD configuration issue, not a security risk for this established package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable scoped package in a large monorepo; missing description is a consistent pattern across the @player-ui namespace. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo package; missing metadata fields are consistent across all @player-ui packages, not spam indicators. | ai | |
| phantom-deps | phantom-dep:timm | AI (phantom-deps): timm is a declared runtime dep in package.json; phantom-dep heuristic false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dep; stable false positive for this package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.0.1 | 4 / 3 | |
| 1.0.0 | 4 / 3 | |
| 0.15.5 | 4 / 2 | |
| 0.15.4 | 4 / 2 | |
| 0.15.3 | 4 / 2 | |
| 0.15.2 | 4 / 2 | |
| 0.15.1 | 4 / 2 | |
| 0.15.0 | 4 / 2 | |
| 0.14.1 | 4 / 2 | |
| 0.14.0 | 4 / 2 | |
| 0.13.0 | 4 / 2 | |
| 0.12.0 | 4 / 2 | |
| 0.11.2 | 4 / 2 | |
| 0.11.1 | 4 / 1 | |
| 0.11.0 | 4 / 1 | |
| 0.10.4 | 4 / 1 | |
| 0.10.3 | 4 / 0 | |
| 0.10.2 | 4 / 0 | |
| 0.10.1 | 4 / 0 | |
| 0.10.0 | 4 / 0 | |
| 0.9.1 | 4 / 0 | |
| 0.8.0 | 4 / 0 | |
| 0.7.3 | 3 / 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.