@teambit/vue-aspect
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 | no-description | AI (npm-metadata): Bit ecosystem package; missing description is common in monorepo-published components. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publisher; provenance not yet enabled but not a blocker for established ecosystem. | ai | |
| dependencies | unvetted-dep:@teambit/schema | AI (dependencies): Internal @teambit ecosystem dep; consistent with Bit platform package family. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Internal @teambit ecosystem dep; consistent with Bit platform package family. | ai | |
| dependencies | unvetted-dep:@teambit/api-reference | AI (dependencies): Internal @teambit ecosystem dep; consistent with Bit platform package family. | ai | |
| dependencies | unvetted-dep:@teambit/documenter.ui.table | AI (dependencies): Internal @teambit ecosystem dep; consistent with Bit platform package family. | ai | |
| dependencies | unvetted-dep:@teambit/ui | AI (dependencies): Internal @teambit ecosystem dep; consistent with Bit platform package family. | ai | |
| dependencies | unvetted-dep:@teambit/semantics.entities.semantic-schema | AI (dependencies): Internal @teambit ecosystem dep; consistent with Bit platform package family. | ai | |
| dependencies | unvetted-dep:@teambit/api-reference.models.api-node-renderer | AI (dependencies): Internal @teambit ecosystem dep; consistent with Bit platform package family. | ai | |
| dependencies | unvetted-dep:@teambit/api-reference.models.api-reference-model | AI (dependencies): Internal @teambit ecosystem dep; consistent with Bit platform package family. | ai | |
| dependencies | unvetted-dep:@teambit/documenter.ui.table-row | AI (dependencies): Internal @teambit ecosystem dep; consistent with Bit platform package family. | ai | |
| dependencies | unvetted-dep:@teambit/cli | AI (dependencies): Internal @teambit ecosystem dep; consistent with Bit platform package family. | ai |
Versions (showing 40 of 340)
| Version | Deps | Published |
|---|---|---|
| 0.0.40 | 12 / 1 | |
| 0.0.39 | 12 / 1 | |
| 0.0.38 | 12 / 1 | |
| 0.0.37 | 12 / 1 | |
| 0.0.36 | 12 / 1 | |
| 0.0.35 | 12 / 1 | |
| 0.0.34 | 12 / 1 | |
| 0.0.33 | 12 / 1 | |
| 0.0.32 | 12 / 1 | |
| 0.0.31 | 12 / 1 | |
| 0.0.30 | 12 / 1 | |
| 0.0.29 | 12 / 1 | |
| 0.0.28 | 12 / 1 | |
| 0.0.27 | 12 / 1 | |
| 0.0.26 | 12 / 1 | |
| 0.0.25 | 12 / 1 | |
| 0.0.24 | 12 / 1 | |
| 0.0.23 | 12 / 1 | |
| 0.0.22 | 12 / 1 | |
| 0.0.21 | 12 / 1 | |
| 0.0.20 | 12 / 1 | |
| 0.0.19 | 12 / 1 | |
| 0.0.18 | 12 / 1 | |
| 0.0.17 | 12 / 1 | |
| 0.0.16 | 12 / 1 | |
| 0.0.15 | 12 / 1 | |
| 0.0.14 | 12 / 1 | |
| 0.0.13 | 12 / 1 | |
| 0.0.12 | 12 / 1 | |
| 0.0.11 | 12 / 1 | |
| 0.0.10 | 12 / 1 | |
| 0.0.9 | 12 / 1 | |
| 0.0.8 | 12 / 1 | |
| 0.0.7 | 12 / 1 | |
| 0.0.6 | 12 / 1 | |
| 0.0.5 | 12 / 1 | |
| 0.0.4 | 12 / 1 | |
| 0.0.3 | 12 / 1 | |
| 0.0.2 | 12 / 1 | |
| 0.0.1 | 12 / 1 |
v0.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.