← Home

xgplayer-subtitles

npm Repository Homepage

外挂字幕组件，目前支持vtt格式的解析

24
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

lixiangfeiorggemstonehongqiongxingleonardo-fu

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Vetted publisher with clean track record; no malicious change accompanying transfer. ai
maintainer-change maintainer-added AI (maintainer-change): Same maintainer transition already vetted; no material code changes in this version. ai

Versions (showing 24 of 24)

Version Deps Published
3.0.26 1 / 0
3.0.25 1 / 0
3.0.24 1 / 0
3.0.23 1 / 0
3.0.22 1 / 0
3.0.21 1 / 0
3.0.20 1 / 0
3.0.19 1 / 0
3.0.18 1 / 0
3.0.17 1 / 0
3.0.16 1 / 0
3.0.15 1 / 0
3.0.14 1 / 0
3.0.13 1 / 0
3.0.12 1 / 0
3.0.11 1 / 0
3.0.10 1 / 0
3.0.9 1 / 0
3.0.8 1 / 0
3.0.7 1 / 0
3.0.6 1 / 0
3.0.5 1 / 0
3.0.4 1 / 0
3.0.3 1 / 0

v3.0.26

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.0.25

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.0.21

2 findings
HIGH Publisher changed: leonardo-fu → gemstone (on 2025-02-24) provenance

This version was published by a different npm account than previous versions on 2025-02-24. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.20

2 findings
HIGH Publisher changed: leonardo-fu → gemstone (on 2024-08-23) provenance

This version was published by a different npm account than previous versions on 2024-08-23. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.19

2 findings
HIGH Publisher changed: leonardo-fu → gemstone (on 2024-07-19) provenance

This version was published by a different npm account than previous versions on 2024-07-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.18

2 findings
HIGH Publisher changed: leonardo-fu → gemstone (on 2024-05-21) provenance

This version was published by a different npm account than previous versions on 2024-05-21. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.