@etohq/access-link
Eto Access Link module: context-aware access management, invitations, and referral links with full approval workflows.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:awilix | AI (phantom-deps): Likely used via DI container config rather than direct import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@etohq/utils | AI (phantom-deps): Same-org dependency; likely re-exported or used indirectly through framework layer. | ai | |
| phantom-deps | phantom-dep:@mikro-orm/core | AI (phantom-deps): Referenced in ORM CLI config files; not a direct import but a legitimate declared dependency. | ai | |
| phantom-deps | phantom-dep:@mikro-orm/migrations | AI (phantom-deps): Referenced in ORM CLI config files; not a direct import but a legitimate declared dependency. | ai | |
| phantom-deps | phantom-dep:@mikro-orm/postgresql | AI (phantom-deps): Referenced in ORM CLI config files; not a direct import but a legitimate declared dependency. | ai |
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.