@stonecrop/nuxt
Nuxt module for Stonecrop
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:next | AI (typosquat): @stonecrop/nuxt is a Nuxt integration module in the stonecrop monorepo, not a typosquat of 'next'. | ai | |
| phantom-deps | phantom-dep:@stonecrop/atable | AI (phantom-deps): Same-org sibling dep; declared in package.json as a runtime dependency, phantom-dep heuristic is a false positive here. | ai |
Versions (showing 16 of 116)
| Version | Deps | Published |
|---|---|---|
| 0.4.15 | 5 / 14 | |
| 0.4.14 | 5 / 14 | |
| 0.4.13 | 5 / 14 | |
| 0.4.12 | 5 / 14 | |
| 0.4.11 | 5 / 14 | |
| 0.4.10 | 5 / 14 | |
| 0.4.9 | 5 / 14 | |
| 0.4.8 | 5 / 14 | |
| 0.4.7 | 5 / 14 | |
| 0.4.6 | 5 / 14 | |
| 0.4.5 | 5 / 14 | |
| 0.4.4 | 5 / 14 | |
| 0.4.3 | 5 / 14 | |
| 0.4.2 | 5 / 14 | |
| 0.4.1 | 5 / 14 | |
| 0.4.0 | 5 / 14 |
v0.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.