@enso-ui/comments
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:@enso-ui/confirmation | AI (phantom-deps): Same-org peer dep; phantom-dep heuristic is a stable false positive for this package family. | ai | |
| phantom-deps | phantom-dep:bulma | AI (phantom-deps): Bulma is a CSS framework referenced in build config, not imported in JS — expected pattern for this package. | ai | |
| phantom-deps | phantom-dep:@enso-ui/ui | AI (phantom-deps): Same-org peer dep; phantom-dep heuristic is a stable false positive for this package family. | ai | |
| phantom-deps | phantom-dep:@enso-ui/card | AI (phantom-deps): Same-org peer dep; phantom-dep heuristic is a stable false positive for this package family. | ai | |
| phantom-deps | phantom-dep:@enso-ui/directives | AI (phantom-deps): Same-org peer dep; phantom-dep heuristic is a stable false positive for this package family. | ai | |
| phantom-deps | phantom-dep:@enso-ui/transitions | AI (phantom-deps): Same-org peer dep; phantom-dep heuristic is a stable false positive for this package family. | ai | |
| phantom-deps | phantom-dep:vue | AI (phantom-deps): Vue is a peer dep declared for config/tooling; not directly imported in source — stable pattern for this org's component packages. | ai | |
| phantom-deps | phantom-dep:textarea-caret | AI (phantom-deps): Vue component library; dep likely used indirectly via component logic, stable FP. | ai | |
| phantom-deps | phantom-dep:@fortawesome/vue-fontawesome | AI (phantom-deps): FontAwesome used in Vue templates; phantom-dep is a stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-svg-core | AI (phantom-deps): FontAwesome used in Vue templates; phantom-dep is a stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@fortawesome/free-solid-svg-icons | AI (phantom-deps): FontAwesome used in Vue templates; phantom-dep is a stable FP for this package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Vue component library; deps used in templates/config, not direct JS imports — stable FP for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 4.2.11 | 5 / 12 | |
| 4.2.10 | 5 / 12 | |
| 4.2.9 | 5 / 12 | |
| 4.2.8 | 5 / 12 | |
| 4.2.7 | 5 / 8 | |
| 4.2.6 | 5 / 8 | |
| 4.2.5 | 5 / 8 | |
| 4.2.4 | 10 / 3 | |
| 4.2.3 | 13 / 0 | |
| 4.2.1 | 13 / 0 | |
| 4.2.0 | 13 / 0 | |
| 4.1.0 | 13 / 0 |
v4.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.