@omnia/tooling-vue
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@babel/helper-module-imports | AI (phantom-deps): Framework-scoped Babel helper; loaded by convention, not a direct import concern. | ai | |
| dependencies | unvetted-dep:@types/zepto | AI (dependencies): TypeScript type definitions only; no runtime risk. | ai | |
| dependencies | unvetted-dep:console-timestamp | AI (dependencies): Logging utility; low risk for a build tooling package. | ai | |
| dependencies | unvetted-dep:csx | AI (dependencies): CSS utility library; consistent with Vue tooling package purpose. | ai | |
| dependencies | unvetted-dep:zepto-webpack | AI (dependencies): Webpack-compatible Zepto build; consistent with bundling tooling. | ai | |
| phantom-deps | phantom-dep:css-loader | AI (phantom-deps): Webpack loader dep; stable false positive for this tooling package. | ai | |
| phantom-deps | phantom-dep:url-loader | AI (phantom-deps): Webpack loader dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:es6-promise | AI (phantom-deps): Polyfill dep referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:file-loader | AI (phantom-deps): Webpack loader dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:less-loader | AI (phantom-deps): Webpack loader dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:null-loader | AI (phantom-deps): Webpack loader dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:sass-loader | AI (phantom-deps): Webpack loader dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:style-loader | AI (phantom-deps): Webpack loader dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:zepto-webpack | AI (phantom-deps): Webpack dep referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:postcss-loader | AI (phantom-deps): Webpack loader dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Framework-scoped type package; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/quill | AI (phantom-deps): Framework-scoped type package; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/zepto | AI (phantom-deps): Framework-scoped type package; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/mousetrap | AI (phantom-deps): Framework-scoped type package; stable false positive. | ai | |
| phantom-deps | phantom-dep:@vue/babel-preset-jsx | AI (phantom-deps): Framework-scoped babel preset; stable false positive. | ai | |
| phantom-deps | phantom-dep:babel-loader | AI (phantom-deps): Webpack loader dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:csx | AI (phantom-deps): Build-tool dep referenced in config files; stable false positive for this tooling package. | ai | |
| phantom-deps | phantom-dep:connect | AI (phantom-deps): Dev-server dep referenced in config files; stable false positive. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): Build-tool dep referenced in config files; stable false positive. | ai | |
| phantom-deps | phantom-dep:typestyle | AI (phantom-deps): Build-tool dep referenced in config files; stable false positive. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Spawns 'dotnet dev-certs' for local HTTPS cert generation; standard dev-tooling pattern, not malicious. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads cached build metadata file by path; benign build-tool pattern stable across versions. | ai |
Versions (showing 51 of 57)
| Version | Deps | Published |
|---|---|---|
| 7.11.10 | 41 / 0 | |
| 7.11.9 | 41 / 0 | |
| 7.11.8 | 41 / 0 | |
| 7.11.7 | 41 / 0 | |
| 7.11.6 | 41 / 0 | |
| 7.11.5 | 41 / 0 | |
| 7.11.4 | 41 / 0 | |
| 7.11.3 | 41 / 0 | |
| 7.11.2 | 41 / 0 | |
| 7.11.1 | 41 / 0 | |
| 7.9.43 | 41 / 0 | |
| 7.9.42 | 41 / 0 | |
| 7.9.41 | 41 / 0 | |
| 7.9.40 | 41 / 0 | |
| 7.9.39 | 41 / 0 | |
| 7.9.38 | 41 / 0 | |
| 7.9.37 | 41 / 0 | |
| 7.9.36 | 41 / 0 | |
| 7.9.35 | 41 / 0 | |
| 7.9.34 | 41 / 0 | |
| 7.9.30 | 41 / 0 | |
| 7.9.29 | 41 / 0 | |
| 7.9.28 | 41 / 0 | |
| 7.9.27 | 41 / 0 | |
| 7.9.26 | 41 / 0 | |
| 7.9.25 | 41 / 0 | |
| 7.9.24 | 41 / 0 | |
| 7.9.23 | 41 / 0 | |
| 7.9.15 | 41 / 0 | |
| 7.9.13 | 41 / 0 | |
| 7.9.12 | 41 / 0 | |
| 7.9.11 | 41 / 0 | |
| 7.9.10 | 41 / 0 | |
| 7.9.7 | 41 / 0 | |
| 7.9.6 | 41 / 0 | |
| 7.9.5 | 41 / 0 | |
| 7.9.4 | 41 / 0 | |
| 7.9.3 | 41 / 0 | |
| 7.9.2 | 41 / 0 | |
| 7.9.1 | 41 / 0 | |
| 7.9.0 | 41 / 0 | |
| 7.8.16 | 41 / 0 | |
| 7.8.15 | 41 / 0 | |
| 7.8.14 | 41 / 0 | |
| 7.8.13 | 41 / 0 | |
| 7.8.12 | 41 / 0 | |
| 7.8.11 | 41 / 0 | |
| 7.8.10 | 41 / 0 | |
| 7.8.9 | 41 / 0 | |
| 7.8.8 | 41 / 0 | |
| 7.8.7 | 41 / 0 |
v7.11.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: andtii.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.