@mux/mux-data-google-ima No license 25 versions

@mux/mux-data-google-ima

npm

25

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

jsanford8dylanjhaphil-muxmux-npmjs

Keywords

google-imacsaivideo-analyticsmux

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Trusted first-party Mux publisher; gitHead absence is a benign publish-env change.	ai	2026/07/07
provenance	publisher-changed	AI (provenance): Publisher change from mux-npmjs to GitHub Actions reflects standard CI/CD migration for the @mux org; stable for this package.	ai	2026/04/26
maintainer-change	maintainer-added	AI (maintainer-change): dylanjha is a known Mux employee; adding team members as maintainers is routine for @mux scoped packages.	ai	2026/04/26
phantom-deps	phantom-dep:mux-embed	AI (phantom-deps): mux-embed is intentionally marked as external in the build scripts; phantom-dep finding is a stable false positive for this package.	ai	2026/04/25

Versions (showing 25 of 25)

Version	Deps	Published
0.3.17	1 / 14	2026-04-27
0.3.16	1 / 13	2026-04-10
0.3.15	1 / 13	2026-02-25
0.3.11	1 / 13	2026-02-18
0.3.4	1 / 13	2026-02-03
0.3.3	1 / 13	2026-01-20
0.3.2	1 / 13	2025-12-17
0.3.1	1 / 13	2025-11-19
0.3.0	1 / 13	2025-10-01
0.2.12	1 / 13	2025-09-05
0.2.11	1 / 13	2025-07-10
0.2.10	1 / 13	2025-07-02
0.2.8	1 / 13	2025-04-07
0.2.7	1 / 13	2025-03-27
0.2.6	1 / 13	2025-03-12
0.2.5	1 / 13	2025-03-10
0.2.4	1 / 13	2025-03-04
0.2.3	1 / 13	2025-02-28
0.2.2	1 / 13	2025-02-18
0.2.1	1 / 13	2025-01-27
0.2.0	1 / 13	2024-12-13
0.1.2	1 / 13	2024-11-26
0.1.1	1 / 13	2024-11-26
0.1.0	1 / 13	2024-11-26
0.0.1	1 / 13	2024-11-25

v0.2.8

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mux-npmjs.

LOW No provenance attestation provenance

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

v0.2.7

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mux-npmjs.

LOW No provenance attestation provenance

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

v0.2.6

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mux-npmjs.

LOW No provenance attestation provenance

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

v0.2.5

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mux-npmjs.

LOW No provenance attestation provenance

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

v0.2.4

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mux-npmjs.

LOW No provenance attestation provenance

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

v0.2.3

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mux-npmjs.

LOW No provenance attestation provenance

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

v0.2.2

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mux-npmjs.

LOW No provenance attestation provenance

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

v0.2.1

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mux-npmjs.

LOW No provenance attestation provenance

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

v0.2.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mux-npmjs.

LOW No provenance attestation provenance

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

v0.1.2

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mux-npmjs.

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

v0.1.0

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.

v0.0.1

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.