@asgardeo/nuxt
Nuxt module for Asgardeo - Authentication and Identity Management
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is used by WSO2's SDK packages as an initial placeholder; consistent across their ecosystem. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Legitimate Nuxt module by WSO2/Asgardeo; name similarity to 'next' is coincidental (nuxt vs next). | ai | |
| dependencies | unvetted-dep:@asgardeo/vue | AI (dependencies): First-party sibling package from the same WSO2/Asgardeo org. | ai | |
| dependencies | unvetted-dep:@asgardeo/node | AI (dependencies): First-party sibling package from the same WSO2/Asgardeo org. | ai | |
| dependencies | unvetted-dep:@asgardeo/browser | AI (dependencies): First-party sibling package from the same WSO2/Asgardeo org. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.2.0 | 6 / 13 | |
| 0.1.8 | 6 / 13 | |
| 0.1.7 | 6 / 13 | |
| 0.1.6 | 6 / 13 | |
| 0.1.5 | 6 / 13 | |
| 0.1.4 | 6 / 13 | |
| 0.1.3 | 6 / 13 | |
| 0.1.2 | 6 / 13 | |
| 0.1.1 | 6 / 13 | |
| 0.1.0 | 6 / 13 | |
| 0.0.0 | 3 / 13 |
v0.2.0
2 findingsPackage name '@asgardeo/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
2 findingsPackage name '@asgardeo/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
2 findingsPackage name '@asgardeo/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
2 findingsPackage name '@asgardeo/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
2 findingsPackage name '@asgardeo/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
2 findingsPackage name '@asgardeo/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
2 findingsPackage name '@asgardeo/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
2 findingsPackage name '@asgardeo/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
2 findingsPackage name '@asgardeo/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
2 findingsPackage name '@asgardeo/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.