@wistia/wistia-player
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/types/embeds/carousel/CarouseItemsList.d.ts | AI (source-diff): Long lines are CSS template literals in a .d.ts file, not obfuscated executable code. | ai | |
| source-diff | obfuscated-file:dist/types/embeds/carousel/channelCarousel/CarouselMedia.d.ts | AI (source-diff): Long lines are CSS template literals in a .d.ts file, not obfuscated executable code. | ai | |
| phantom-deps | phantom-dep:mux-embed | AI (phantom-deps): Build/config-time dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:lodash.merge | AI (phantom-deps): Build/config-time dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:dotenv-webpack | AI (phantom-deps): Build/config-time dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:iso8601-duration | AI (phantom-deps): Build/config-time dependency; stable pattern for this package. | ai |
Versions (showing 100 of 192)
| Version | Deps | Published |
|---|---|---|
| 0.7.11 | 5 / 18 | |
| 0.7.10 | 5 / 18 | |
| 0.7.9 | 5 / 18 | |
| 0.7.8 | 5 / 18 | |
| 0.7.7 | 5 / 18 | |
| 0.7.6 | 5 / 18 | |
| 0.7.5 | 5 / 18 | |
| 0.7.4 | 5 / 18 | |
| 0.7.2 | 5 / 18 | |
| 0.7.1 | 5 / 18 | |
| 0.7.0 | 5 / 18 | |
| 0.6.22 | 5 / 18 | |
| 0.6.21 | 5 / 18 | |
| 0.6.20 | 5 / 18 | |
| 0.6.19 | 5 / 18 | |
| 0.6.18 | 5 / 18 | |
| 0.6.17 | 5 / 18 | |
| 0.6.16 | 5 / 18 | |
| 0.6.15 | 5 / 18 | |
| 0.6.14 | 5 / 18 | |
| 0.6.13 | 5 / 18 | |
| 0.6.12 | 5 / 18 | |
| 0.6.11 | 5 / 18 | |
| 0.6.10 | 5 / 18 | |
| 0.6.9 | 5 / 18 | |
| 0.6.8 | 5 / 18 | |
| 0.6.7 | 5 / 18 | |
| 0.6.6 | 5 / 18 | |
| 0.6.5 | 5 / 18 | |
| 0.6.4 | 5 / 18 | |
| 0.6.3 | 5 / 18 | |
| 0.6.2 | 5 / 18 | |
| 0.6.1 | 5 / 18 | |
| 0.6.0 | 5 / 18 | |
| 0.5.1 | 5 / 18 | |
| 0.5.0 | 5 / 18 | |
| 0.4.3 | 5 / 18 | |
| 0.4.2 | 5 / 18 | |
| 0.4.1 | 5 / 18 | |
| 0.4.0 | 5 / 18 | |
| 0.3.19 | 5 / 18 | |
| 0.3.18 | 5 / 18 | |
| 0.3.17 | 5 / 18 | |
| 0.3.16 | 5 / 18 | |
| 0.3.15 | 5 / 18 | |
| 0.3.14 | 5 / 18 | |
| 0.3.13 | 5 / 18 | |
| 0.3.12 | 5 / 18 | |
| 0.3.11 | 5 / 18 | |
| 0.3.8 | 5 / 18 | |
| 0.3.7 | 5 / 18 | |
| 0.3.6 | 5 / 18 | |
| 0.3.5 | 5 / 18 | |
| 0.3.4 | 5 / 18 | |
| 0.3.3 | 5 / 18 | |
| 0.3.2 | 5 / 18 | |
| 0.3.1 | 5 / 18 | |
| 0.3.0 | 5 / 18 | |
| 0.2.1 | 5 / 18 | |
| 0.2.0 | 5 / 18 | |
| 0.1.18 | 5 / 18 | |
| 0.1.17 | 5 / 18 | |
| 0.1.16 | 5 / 18 | |
| 0.1.15 | 5 / 18 | |
| 0.1.14 | 5 / 18 | |
| 0.1.13 | 5 / 18 | |
| 0.1.12 | 5 / 18 | |
| 0.1.11 | 5 / 18 | |
| 0.1.10 | 5 / 18 | |
| 0.1.9 | 5 / 18 | |
| 0.1.8 | 5 / 18 | |
| 0.1.7 | 5 / 18 | |
| 0.1.6 | 5 / 18 | |
| 0.1.5 | 5 / 18 | |
| 0.1.4 | 5 / 18 | |
| 0.1.2 | 5 / 18 | |
| 0.1.1 | 5 / 18 | |
| 0.1.0 | 5 / 18 | |
| 0.0.115 | 5 / 18 | |
| 0.0.114 | 5 / 18 | |
| 0.0.113 | 5 / 18 | |
| 0.0.112 | 5 / 18 | |
| 0.0.111 | 5 / 18 | |
| 0.0.110 | 5 / 18 | |
| 0.0.109 | 5 / 18 | |
| 0.0.108 | 5 / 18 | |
| 0.0.107 | 5 / 18 | |
| 0.0.106 | 5 / 18 | |
| 0.0.105 | 5 / 18 | |
| 0.0.104 | 5 / 18 | |
| 0.0.103 | 5 / 18 | |
| 0.0.102 | 5 / 18 | |
| 0.0.101 | 5 / 18 | |
| 0.0.100 | 5 / 18 | |
| 0.0.99 | 5 / 18 | |
| 0.0.98 | 5 / 18 | |
| 0.0.97 | 5 / 18 | |
| 0.0.96 | 5 / 18 | |
| 0.0.95 | 5 / 18 | |
| 0.0.94 | 5 / 18 |
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.