@enso-ui/filters
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:vuex | AI (phantom-deps): Vue state management declared in dependencies; typical for Vue component libraries. | ai | |
| dependencies | unvetted-dep:bulma | AI (dependencies): bulma is a well-known CSS framework; stable false positive for this UI package. | ai | |
| dependencies | unvetted-dep:@enso-ui/strings | AI (dependencies): Same org scope (@enso-ui); expected sibling dependency, not a risk. | ai | |
| phantom-deps | phantom-dep:@enso-ui/select | AI (phantom-deps): Same-org peer dep; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@enso-ui/ui | AI (phantom-deps): Same-org peer dep; not directly imported by design across enso-ui packages. | ai | |
| phantom-deps | phantom-dep:@enso-ui/switch | AI (phantom-deps): Same-org peer dep; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@enso-ui/strings | AI (phantom-deps): Same-org peer dep; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@enso-ui/datepicker | AI (phantom-deps): Same-org peer dep; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@enso-ui/transitions | AI (phantom-deps): Same-org peer dep; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:vue | AI (phantom-deps): Vue is a peer dep for a Vue component library; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:bulma | AI (phantom-deps): CSS framework declared as dep but imported via config/build; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@fortawesome/free-solid-svg-icons | AI (phantom-deps): Icon library used via Vue component registration; stable false positive for this UI package. | ai | |
| phantom-deps | phantom-dep:v-tooltip | AI (phantom-deps): Referenced in config/template context; stable false positive for this UI package. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-svg-core | AI (phantom-deps): Icon library used via Vue component registration; stable false positive for this UI package. | ai | |
| phantom-deps | phantom-dep:@fortawesome/vue-fontawesome | AI (phantom-deps): Icon library used via Vue component registration; stable false positive for this UI package. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Likely used indirectly via Vue component templates or config; stable pattern for this UI component package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 3.3.16 | 5 / 13 | |
| 3.3.15 | 5 / 13 | |
| 3.3.14 | 5 / 13 | |
| 3.3.13 | 5 / 13 | |
| 3.3.11 | 5 / 13 | |
| 3.3.9 | 5 / 13 | |
| 3.3.7 | 5 / 13 | |
| 3.3.6 | 5 / 9 | |
| 3.3.5 | 5 / 9 | |
| 3.3.4 | 5 / 9 | |
| 3.3.3 | 11 / 3 | |
| 3.3.2 | 11 / 3 | |
| 3.3.1 | 14 / 0 | |
| 3.3.0 | 14 / 0 | |
| 3.2.0 | 14 / 0 | |
| 3.1.8 | 13 / 9 | |
| 3.1.2 | 13 / 9 | |
| 3.1.1 | 13 / 9 | |
| 3.1.0 | 13 / 9 | |
| 3.0.28 | 13 / 9 |
v3.3.16
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (vlad.chv) than the most recent previously approved version (aocneanu) on 2026-06-02, but vlad.chv is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.