@freteclick/quasar-orders-ui
Frete Click Quotations Quasar UI Component
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Internal org UI component; lack of provenance is consistent across all 26 versions and poses no active risk. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.2.60 | 0 / 0 | |
| 1.2.56 | 0 / 0 | |
| 1.2.55 | 0 / 0 | |
| 1.2.52 | 0 / 0 |
v1.2.56
2 findingsMaintainer email '[email protected]' uses domain 'starfez.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.55
2 findingsMaintainer email '[email protected]' uses domain 'starfez.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.52
2 findingsMaintainer email '[email protected]' uses domain 'starfez.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.