@enso-ui/logs
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:vue | AI (phantom-deps): Vue is a peer dependency declared for compatibility; standard pattern for Vue component packages. | ai | |
| phantom-deps | phantom-dep:@enso-ui/card | AI (phantom-deps): Same-org sibling dep; indirect usage via component composition is expected. | ai | |
| phantom-deps | phantom-dep:@enso-ui/directives | AI (phantom-deps): Same-org sibling dep; indirect usage via component composition is expected. | ai | |
| phantom-deps | phantom-dep:@enso-ui/confirmation | AI (phantom-deps): Same-org sibling dep; indirect usage via component composition is expected. | ai | |
| typosquat | typosquat.levenshtein:log4js | AI (typosquat): Scoped @enso-ui package; no relation to log4js. Levenshtein match is coincidental. | ai | |
| phantom-deps | phantom-dep:@fortawesome/vue-fontawesome | AI (phantom-deps): @fortawesome/vue-fontawesome is a direct dependency in package.json; likely used via Vue plugin registration rather than direct import. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @enso-ui package; no relation to cors. Levenshtein match is coincidental. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.2.5 | 3 / 4 | |
| 5.2.3 | 3 / 5 | |
| 5.2.2 | 7 / 1 | |
| 5.2.1 | 8 / 0 | |
| 5.2.0 | 8 / 0 | |
| 5.1.0 | 8 / 0 |
v5.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.