@freteclick/quasar-quote-ui
Frete Click Quote 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): Established package with 358 versions; lack of provenance is consistent across all prior releases. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.3.55 | 0 / 0 | |
| 2.3.53 | 0 / 0 | |
| 2.3.52 | 0 / 0 | |
| 2.3.51 | 0 / 0 | |
| 2.3.49 | 0 / 0 | |
| 2.3.47 | 0 / 0 | |
| 2.3.45 | 0 / 0 | |
| 2.3.44 | 0 / 0 | |
| 2.3.42 | 0 / 0 | |
| 2.3.41 | 0 / 0 | |
| 2.3.40 | 0 / 0 | |
| 2.3.39 | 0 / 0 |
v2.3.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. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.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.
v2.3.51
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.49
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.47
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.45
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.
v2.3.44
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.42
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.41
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.40
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.39
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.