@player-ui/computed-properties-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 | missing-githead | AI (provenance): Large monorepo with 584 versions; publish environment change is plausible and no material code changes detected vs prior version. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped monorepo package; missing description is a consistent pattern across the @player-ui suite, not a malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all @player-ui versions; consistent pattern for this publisher. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; implicit transitive use is normal in compiled packages. | ai | |
| phantom-deps | phantom-dep:tapable-ts | AI (phantom-deps): tapable-ts referenced in config/build files; phantom-dep false positive for this monorepo-style package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo plugin package; missing metadata signals are expected for internal sub-packages. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.0.1 | 2 / 5 | |
| 1.0.0 | 2 / 5 | |
| 0.15.5 | 2 / 5 | |
| 0.15.4 | 2 / 5 | |
| 0.15.3 | 2 / 5 | |
| 0.15.2 | 2 / 5 | |
| 0.15.1 | 2 / 5 | |
| 0.15.0 | 2 / 5 | |
| 0.14.1 | 2 / 5 | |
| 0.14.0 | 2 / 5 | |
| 0.13.0 | 2 / 5 | |
| 0.12.0 | 2 / 5 | |
| 0.11.2 | 2 / 5 | |
| 0.11.1 | 2 / 5 | |
| 0.11.0 | 2 / 5 | |
| 0.10.4 | 2 / 5 | |
| 0.10.3 | 2 / 5 | |
| 0.10.2 | 2 / 5 | |
| 0.10.1 | 2 / 5 | |
| 0.10.0 | 2 / 5 | |
| 0.9.1 | 2 / 5 | |
| 0.8.0 | 2 / 5 | |
| 0.7.3 | 2 / 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. Consider requesting the maintainer enable provenance via CI/CD.
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.