@enso-ui/auth
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/laravel-validation | AI (phantom-deps): Same-org dep used in templates/config — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:zxcvbn | AI (phantom-deps): Password-strength lib used indirectly via component config; stable false positive for this auth package. | ai | |
| phantom-deps | phantom-dep:@enso-ui/forms | AI (phantom-deps): Same-org dep used in templates/config, not directly imported — expected pattern for this package. | ai | |
| phantom-deps | phantom-dep:@enso-ui/directives | AI (phantom-deps): Same-org dep used in templates/config — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:vue | AI (phantom-deps): Vue is a peer dep used in config/templates, not directly imported in JS — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-svg-core | AI (phantom-deps): FontAwesome config reference; stable pattern for this UI library. | ai | |
| phantom-deps | phantom-dep:@fortawesome/free-solid-svg-icons | AI (phantom-deps): FontAwesome config reference; stable pattern for this UI library. | ai | |
| phantom-deps | phantom-dep:@fortawesome/vue-fontawesome | AI (phantom-deps): FontAwesome config reference; stable pattern for this UI library. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 3.1.24 | 3 / 11 | |
| 3.1.22 | 3 / 11 | |
| 3.1.20 | 3 / 11 | |
| 3.1.19 | 3 / 11 | |
| 3.1.18 | 4 / 11 | |
| 3.1.17 | 4 / 11 | |
| 3.1.16 | 4 / 11 | |
| 3.1.15 | 4 / 11 | |
| 3.1.14 | 4 / 11 | |
| 3.1.13 | 4 / 11 | |
| 3.1.12 | 4 / 11 | |
| 3.1.11 | 4 / 6 | |
| 3.1.9 | 4 / 6 | |
| 3.1.8 | 4 / 6 | |
| 3.1.7 | 4 / 6 | |
| 3.1.6 | 8 / 2 | |
| 3.1.2 | 10 / 0 | |
| 3.1.1 | 10 / 0 | |
| 3.1.0 | 10 / 0 |
v3.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.6
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.