@enso-ui/users
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@enso-ui/modal | AI (dependencies): Same-org sibling dependency; stable pattern across all @enso-ui/users versions. | ai | |
| dependencies | unvetted-dep:@enso-ui/divider | AI (dependencies): Same-org sibling dependency; stable pattern across all @enso-ui/users versions. | ai | |
| dependencies | unvetted-dep:@enso-ui/uploader | AI (dependencies): Same-org sibling dependency; stable pattern across all @enso-ui/users versions. | ai | |
| dependencies | unvetted-dep:@enso-ui/accessories | AI (dependencies): Same-org sibling dependency; stable pattern across all @enso-ui/users versions. | ai | |
| dependencies | unvetted-dep:@enso-ui/confirmation | AI (dependencies): Same-org sibling dependency; stable pattern across all @enso-ui/users versions. | ai | |
| phantom-deps | phantom-dep:vuex | AI (phantom-deps): vuex is a peer/config-level dep for Vue 3 ecosystem packages; not directly imported but legitimately declared. | ai | |
| phantom-deps | phantom-dep:@enso-ui/divider | AI (phantom-deps): Same-org sibling package; referenced via config/re-export pattern. | ai | |
| phantom-deps | phantom-dep:@enso-ui/uploader | AI (phantom-deps): Same-org sibling package; referenced via config/re-export pattern. | ai | |
| phantom-deps | phantom-dep:@enso-ui/directives | AI (phantom-deps): Same-org sibling package; referenced via config/re-export pattern. | ai | |
| phantom-deps | phantom-dep:vue | AI (phantom-deps): Vue is a peer/config dependency for a Vue component library; not directly imported in source is expected. | ai | |
| phantom-deps | phantom-dep:@enso-ui/confirmation | AI (phantom-deps): Same-org sibling package; referenced via config/re-export pattern. | ai | |
| phantom-deps | phantom-dep:@fortawesome/vue-fontawesome | AI (phantom-deps): FontAwesome Vue adapter; referenced in config files, not direct import — expected for Vue component library. | ai | |
| phantom-deps | phantom-dep:@fortawesome/free-brands-svg-icons | AI (phantom-deps): Icon set referenced in config; not direct import is expected pattern for this library. | ai | |
| phantom-deps | phantom-dep:@enso-ui/accessories | AI (phantom-deps): Same-org sibling package; referenced via config/re-export pattern. | ai | |
| phantom-deps | phantom-dep:@enso-ui/auth | AI (phantom-deps): Same-org sibling package; referenced via config/re-export pattern, not direct import. | ai | |
| phantom-deps | phantom-dep:@enso-ui/tabs | AI (phantom-deps): Same-org sibling package; referenced via config/re-export pattern. | ai | |
| phantom-deps | phantom-dep:@enso-ui/forms | AI (phantom-deps): Same-org sibling package; referenced via config/re-export pattern. | ai | |
| phantom-deps | phantom-dep:@enso-ui/modal | AI (phantom-deps): Same-org sibling package; referenced via config/re-export pattern. | ai | |
| phantom-deps | phantom-dep:@enso-ui/tables | AI (phantom-deps): Same-org sibling package; referenced via config/re-export pattern. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 3.1.12 | 4 / 18 | |
| 3.1.11 | 4 / 18 | |
| 3.1.10 | 4 / 18 | |
| 3.1.9 | 4 / 18 | |
| 3.1.8 | 4 / 13 | |
| 3.1.7 | 4 / 13 | |
| 3.1.5 | 4 / 13 | |
| 3.1.4 | 15 / 2 | |
| 3.1.3 | 17 / 0 | |
| 3.1.1 | 17 / 0 | |
| 3.1.0 | 17 / 0 | |
| 3.0.5 | 17 / 9 |
v3.1.12
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-05-26, 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.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.