@bililive-tools/manager
Batch scheduling recorders
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@renmu/fluent-ffmpeg | AI (dependencies): First-party fork by the same author (renmu123); consistent with package purpose across versions. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established package with 21 versions and matching author; no other takeover indicators present. | ai | |
| provenance | no-provenance | AI (provenance): Established package with consistent publish history; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): fs-extra is a declared runtime dependency; phantom-dep false positive for this package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.17.0 | 9 / 0 | |
| 1.16.2 | 9 / 0 | |
| 1.16.1 | 9 / 0 | |
| 1.16.0 | 9 / 0 | |
| 1.14.1 | 9 / 0 | |
| 1.13.0 | 9 / 0 | |
| 1.12.0 | 9 / 0 | |
| 1.11.1 | 9 / 0 | |
| 1.11.0 | 9 / 0 | |
| 1.10.0 | 9 / 0 | |
| 1.9.0 | 9 / 0 | |
| 1.8.0 | 9 / 0 | |
| 1.6.1 | 9 / 0 | |
| 1.6.0 | 9 / 0 | |
| 1.5.0 | 9 / 0 | |
| 1.4.1 | 9 / 0 | |
| 1.4.0 | 9 / 0 | |
| 1.3.0 | 8 / 0 | |
| 1.2.1 | 8 / 0 | |
| 1.2.0 | 8 / 0 | |
| 1.1.0 | 8 / 0 | |
| 1.0.1 | 8 / 0 | |
| 1.0.0 | 5 / 0 |
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.