@quasar/app-vite
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): picomatch is a well-known, minimal glob library; normal dependency addition for a build CLI. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): Config-library env filtering, expected for CLI devserver tooling. | ai | |
| dependencies | unvetted-dep:@quasar/art | AI (dependencies): First-party Quasar-scoped package, not a supply-chain risk. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used in a proxy getter for config objects, not evasive code. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Template engine compiling user-authored templates, standard pattern. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Build tool passing process.env to child processes is standard; not credential exfiltration. | ai | |
| phantom-deps | phantom-dep:sass-embedded | AI (phantom-deps): Optional CSS preprocessor referenced in config; not directly imported by the tool itself. | ai | |
| phantom-deps | phantom-dep:@types/chrome | AI (phantom-deps): Framework-scoped type declaration; loaded by convention in Quasar projects. | ai | |
| phantom-deps | phantom-dep:@types/cordova | AI (phantom-deps): Framework-scoped type declaration; loaded by convention in Quasar projects. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): Framework-scoped type declaration; loaded by convention in Quasar SSR projects. | ai | |
| phantom-deps | phantom-dep:@types/compression | AI (phantom-deps): Framework-scoped type declaration; loaded by convention in Quasar SSR projects. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 3.2.0 | 32 / 6 | |
| 3.1.0 | 32 / 6 | |
| 3.0.1 | 31 / 6 | |
| 3.0.0 | 31 / 6 | |
| 2.6.2 | 37 / 8 | |
| 2.6.1 | 37 / 8 | |
| 2.6.0 | 37 / 8 | |
| 2.5.4 | 37 / 8 | |
| 2.5.3 | 37 / 8 | |
| 2.5.2 | 37 / 10 | |
| 2.5.1 | 37 / 10 | |
| 2.5.0 | 37 / 10 | |
| 2.4.1 | 37 / 10 | |
| 2.4.0 | 37 / 10 | |
| 2.3.0 | 37 / 10 | |
| 2.2.1 | 37 / 10 | |
| 2.2.0 | 37 / 10 | |
| 2.1.4 | 37 / 10 | |
| 2.1.3 | 36 / 10 | |
| 2.1.2 | 36 / 10 | |
| 2.1.1 | 36 / 10 | |
| 2.1.0 | 36 / 10 | |
| 2.0.9 | 36 / 10 | |
| 2.0.8 | 36 / 10 | |
| 2.0.7 | 35 / 10 | |
| 2.0.6 | 35 / 10 | |
| 2.0.5 | 35 / 10 | |
| 2.0.4 | 35 / 10 | |
| 2.0.3 | 35 / 10 | |
| 2.0.2 | 35 / 10 | |
| 2.0.1 | 35 / 10 | |
| 2.0.0 | 35 / 10 |
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.