react-native-video
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
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 6.19.2 | 0 / 20 | |
| 6.19.1 | 0 / 19 | |
| 6.19.0 | 0 / 19 | |
| 6.18.0 | 0 / 19 | |
| 6.17.0 | 0 / 19 | |
| 6.16.1 | 0 / 19 | |
| 6.16.0 | 0 / 19 | |
| 6.15.0 | 0 / 19 | |
| 6.14.1 | 0 / 19 | |
| 6.14.0 | 0 / 19 | |
| 6.13.0 | 0 / 18 | |
| 6.12.0 | 0 / 18 | |
| 6.11.0 | 0 / 18 | |
| 6.10.2 | 0 / 18 | |
| 6.10.1 | 0 / 18 | |
| 6.10.0 | 0 / 18 | |
| 6.9.1 | 0 / 17 | |
| 6.9.0 | 0 / 17 | |
| 6.8.2 | 0 / 17 | |
| 6.8.1 | 0 / 17 | |
| 6.8.0 | 0 / 17 | |
| 6.7.0 | 0 / 17 | |
| 6.6.4 | 0 / 17 | |
| 6.6.3 | 0 / 17 | |
| 6.6.2 | 0 / 17 | |
| 6.6.1 | 0 / 17 | |
| 6.6.0 | 0 / 17 | |
| 6.5.0 | 0 / 17 | |
| 6.4.5 | 0 / 17 | |
| 6.4.4 | 0 / 17 | |
| 6.4.3 | 0 / 17 | |
| 6.4.2 | 0 / 17 | |
| 6.4.1 | 0 / 17 | |
| 6.4.0 | 0 / 17 | |
| 6.3.0 | 0 / 16 | |
| 6.2.0 | 0 / 16 | |
| 6.1.2 | 0 / 16 | |
| 6.1.1 | 0 / 16 | |
| 6.1.0 | 0 / 16 | |
| 6.0.0 | 0 / 16 |
v6.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (krzysztof_moch) than the most recent previously approved version (olivier.bouillet) on 2025-04-06, but krzysztof_moch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.11.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (krzysztof_moch) than the most recent previously approved version (olivier.bouillet) on 2025-03-16, but krzysztof_moch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (olivier.bouillet) than the most recent previously approved version (krzysztof_moch) on 2025-01-22, but olivier.bouillet is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (krzysztof_moch) than the most recent previously approved version (olivier.bouillet) on 2025-01-04, but krzysztof_moch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (krzysztof_moch) than the most recent previously approved version (olivier.bouillet) on 2024-11-17, but krzysztof_moch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.7.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (olivier.bouillet) than the most recent previously approved version (krzysztof_moch) on 2024-10-17, but olivier.bouillet is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (olivier.bouillet) than the most recent previously approved version (krzysztof_moch) on 2024-09-18, but olivier.bouillet is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.6.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (krzysztof_moch) than the most recent previously approved version (olivier.bouillet) on 2024-09-18, but krzysztof_moch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.5.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (olivier.bouillet) than the most recent previously approved version (krzysztof_moch) on 2024-09-04, but olivier.bouillet is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.4.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (olivier.bouillet) than the most recent previously approved version (krzysztof_moch) on 2024-08-17, but olivier.bouillet is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (krzysztof_moch) than the most recent previously approved version (olivier.bouillet) on 2024-07-11, but krzysztof_moch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (olivier.bouillet) than the most recent previously approved version (krzysztof_moch) on 2024-06-07, but olivier.bouillet is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.1.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (olivier.bouillet) than the most recent previously approved version (krzysztof_moch) on 2024-05-23, but olivier.bouillet is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (olivier.bouillet) than the most recent previously approved version (krzysztof_moch) on 2024-05-22, but olivier.bouillet is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.