@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, so a manually published version cannot be tied back to a reviewed commit.
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 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 3.3.17 | 5 / 13 | |
| 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 | |
| 3.0.27 | 13 / 9 | |
| 3.0.26 | 13 / 9 | |
| 3.0.25 | 13 / 9 | |
| 3.0.24 | 13 / 9 | |
| 3.0.23 | 13 / 9 | |
| 3.0.22 | 13 / 9 | |
| 3.0.21 | 13 / 9 | |
| 3.0.20 | 13 / 9 | |
| 3.0.19 | 13 / 9 | |
| 3.0.18 | 13 / 9 | |
| 3.0.17 | 13 / 9 | |
| 3.0.16 | 13 / 9 | |
| 3.0.15 | 13 / 9 | |
| 3.0.14 | 13 / 9 | |
| 3.0.13 | 13 / 9 | |
| 3.0.12 | 13 / 9 | |
| 3.0.11 | 13 / 9 | |
| 3.0.10 | 13 / 9 | |
| 3.0.9 | 13 / 9 | |
| 3.0.8 | 13 / 9 | |
| 3.0.7 | 13 / 9 | |
| 3.0.6 | 13 / 9 | |
| 3.0.5 | 13 / 9 | |
| 3.0.4 | 13 / 9 | |
| 3.0.2 | 12 / 9 | |
| 3.0.1 | 12 / 9 | |
| 3.0.0 | 12 / 9 |
v3.3.17
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 (aocneanu) than the most recent previously approved version (vlad.chv) on 2026-07-02, but aocneanu 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.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.20
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 (aocneanu) than the most recent previously approved version (gandesc) on 2022-10-25, but aocneanu 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.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
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 (gandesc) than the most recent previously approved version (aocneanu) on 2021-11-18, but gandesc 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.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
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 (aocneanu) than the most recent previously approved version (gandesc) on 2021-11-17, but aocneanu 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.0.4
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 (gandesc) than the most recent previously approved version (aocneanu) on 2021-11-16, but gandesc 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.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.