@1001-digital/layers.base
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 |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Absolute size (12KB) is small; growth across patch versions is benign for an active Nuxt layer package. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; no provenance is the norm for this publisher. | ai | |
| phantom-deps | phantom-dep:@types/luxon | AI (phantom-deps): Framework-scoped type package; loaded by convention in Nuxt ecosystem. | ai | |
| phantom-deps | phantom-dep:reka-ui | AI (phantom-deps): Config-referenced UI framework dependency; stable pattern for this Nuxt package. | ai | |
| phantom-deps | phantom-dep:@vueuse/core | AI (phantom-deps): Config-referenced Vue composables; standard pattern for Nuxt packages. | ai | |
| phantom-deps | phantom-dep:modern-normalize | AI (phantom-deps): Config-referenced CSS normalization; stable for this package. | ai | |
| phantom-deps | phantom-dep:@iconify-json/lucide | AI (phantom-deps): Icon data package referenced in config files, not directly imported — expected pattern. | ai | |
| phantom-deps | phantom-dep:@iconify-json/simple-icons | AI (phantom-deps): Icon data package referenced in config files, not directly imported — expected pattern. | ai | |
| phantom-deps | phantom-dep:@1001-digital/styles | AI (phantom-deps): Same-org scoped package used via Nuxt layer convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@nuxt/icon | AI (phantom-deps): Framework-scoped Nuxt icon package loaded by convention, not direct import. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 2.0.33 | 5 / 6 | |
| 2.0.32 | 5 / 6 | |
| 2.0.31 | 5 / 6 | |
| 2.0.25 | 5 / 6 | |
| 2.0.24 | 5 / 6 | |
| 2.0.23 | 5 / 6 | |
| 2.0.22 | 5 / 6 | |
| 2.0.21 | 5 / 6 | |
| 2.0.18 | 5 / 6 | |
| 2.0.17 | 5 / 6 | |
| 2.0.15 | 5 / 6 | |
| 2.0.13 | 5 / 6 | |
| 2.0.11 | 5 / 6 | |
| 2.0.10 | 5 / 6 | |
| 2.0.8 | 5 / 6 | |
| 2.0.6 | 5 / 6 | |
| 2.0.5 | 5 / 6 | |
| 2.0.4 | 5 / 6 | |
| 1.4.0 | 5 / 6 | |
| 1.2.0 | 5 / 6 | |
| 1.1.0 | 5 / 6 | |
| 0.0.31 | 8 / 6 | |
| 0.0.30 | 8 / 6 | |
| 0.0.29 | 8 / 6 | |
| 0.0.28 | 8 / 6 | |
| 0.0.27 | 8 / 6 | |
| 0.0.26 | 8 / 6 | |
| 0.0.25 | 8 / 6 | |
| 0.0.24 | 8 / 6 | |
| 0.0.23 | 8 / 6 | |
| 0.0.22 | 8 / 6 | |
| 0.0.21 | 8 / 6 | |
| 0.0.20 | 8 / 6 | |
| 0.0.19 | 8 / 6 | |
| 0.0.18 | 8 / 6 | |
| 0.0.17 | 7 / 6 | |
| 0.0.16 | 7 / 6 | |
| 0.0.15 | 7 / 6 | |
| 0.0.14 | 7 / 6 | |
| 0.0.13 | 5 / 8 | |
| 0.0.12 | 5 / 8 | |
| 0.0.11 | 5 / 8 | |
| 0.0.10 | 5 / 8 | |
| 0.0.9 | 5 / 8 | |
| 0.0.8 | 5 / 8 | |
| 0.0.7 | 5 / 8 | |
| 0.0.6 | 5 / 8 | |
| 0.0.5 | 5 / 8 | |
| 0.0.4 | 4 / 9 | |
| 0.0.3 | 3 / 8 | |
| 0.0.2 | 3 / 8 |
v2.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.