@frontegg/vue-ui
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Signals reflect missing metadata in an early SDK release, not spam/malware indicators. | ai | |
| dependencies | unvetted-dep:owasp-password-strength-test | AI (dependencies): owasp-password-strength-test is a legitimate, well-known OWASP library; stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.2.0 | 6 / 29 | |
| 0.1.3 | 6 / 29 | |
| 0.1.2 | 6 / 29 | |
| 0.1.1 | 7 / 29 | |
| 0.1.0 | 7 / 29 |
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.