@picovoice/rhino-web-vue
Vue component (renderless) for Rhino Web SDK
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/esm/index.js | AI (source-diff): Base64 web-worker bundle from rollup-plugin-web-worker-loader, not obfuscation. | ai | |
| source-diff | encoded-string-file:dist/esm/index.min.js | AI (source-diff): Minified bundle output, same worker-loader pattern. | ai | |
| source-diff | encoded-string-file:dist/iife/index.js | AI (source-diff): Base64 web-worker bundle, standard build artifact. | ai | |
| source-diff | encoded-string-file:dist/iife/index.min.js | AI (source-diff): Minified bundle output, same worker-loader pattern. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer matches known prior publisher per provenance INFO note. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.1.3 | 1 / 17 | |
| 2.1.2 | 1 / 17 | |
| 2.1.1 | 1 / 17 | |
| 2.1.0 | 1 / 17 | |
| 2.0.2 | 1 / 17 | |
| 2.0.1 | 0 / 17 | |
| 2.0.0 | 0 / 16 |
v2.1.2
7 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dynamix70.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dynamix70) than the most recent previously approved version (kyeo) on 2022-03-17, but dynamix70 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.
v2.1.1
5 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
7 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ilavery.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ilavery) than the most recent previously approved version (kyeo) on 2022-01-19, but ilavery 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.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.