@awes-io/nuxt-auth
v2.0
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@awes-io/ui | AI (phantom-deps): Same org scope; likely re-exported rather than directly imported in this Nuxt module. | ai | |
| phantom-deps | phantom-dep:@awes-io/vue-mc | AI (phantom-deps): Same org scope; likely re-exported rather than directly imported in this Nuxt module. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.16.8 | 5 / 18 | |
| 2.16.5 | 5 / 18 | |
| 2.16.4 | 5 / 18 | |
| 2.16.3 | 5 / 18 |
v2.16.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.