@freteclick/quasar-common-ui
FreteClick Common 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; no provenance is common and not a disqualifier here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.102 | 0 / 0 | |
| 1.0.98 | 0 / 0 | |
| 1.0.97 | 0 / 0 | |
| 1.0.96 | 0 / 0 | |
| 1.0.95 | 0 / 0 |
v1.0.98
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.0.97
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.0.96
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.0.95
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.