@enso-ui/documents
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher matches original author; 34 approved packages, no rejections; long-dormant org package resuming maintenance. | ai | |
| phantom-deps | phantom-dep:@enso-ui/ui | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo-style packages. | ai | |
| phantom-deps | phantom-dep:@enso-ui/files | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo-style packages. | ai | |
| phantom-deps | phantom-dep:@enso-ui/mixins | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo-style packages. | ai | |
| phantom-deps | phantom-dep:@enso-ui/uploader | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo-style packages. | ai | |
| phantom-deps | phantom-dep:@enso-ui/transitions | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo-style packages. | ai | |
| phantom-deps | phantom-dep:@enso-ui/confirmation | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo-style packages. | ai | |
| phantom-deps | phantom-dep:vue | AI (phantom-deps): Vue is a peer dep for a Vue component library; not directly imported in source is expected. | ai | |
| phantom-deps | phantom-dep:bulma | AI (phantom-deps): CSS framework declared as dep, referenced in config/build; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Utility lib used indirectly via config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@enso-ui/card | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo-style packages. | ai | |
| phantom-deps | phantom-dep:@fortawesome/vue-fontawesome | AI (phantom-deps): Config-file reference in Vue component library; stable pattern. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-svg-core | AI (phantom-deps): Config-file reference in Vue component library; stable pattern. | ai | |
| phantom-deps | phantom-dep:@fortawesome/free-solid-svg-icons | AI (phantom-deps): Config-file reference in Vue component library; stable pattern. | ai | |
| phantom-deps | phantom-dep:v-tooltip | AI (phantom-deps): Config-file reference in Vue component library; stable pattern. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): Config-file reference in Vue component library; stable pattern. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.2.7 | 5 / 10 | |
| 4.2.6 | 5 / 10 | |
| 4.2.5 | 5 / 10 | |
| 4.2.4 | 5 / 10 | |
| 4.2.3 | 5 / 10 | |
| 4.2.2 | 12 / 3 | |
| 4.2.1 | 15 / 0 | |
| 4.2.0 | 15 / 0 | |
| 4.1.0 | 15 / 0 |
v4.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.