@lemonldap-ng/session
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:@lemonldap-ng/crypto | AI (dependencies): Same-org dependency within the lemonldap-ng namespace; expected and stable for this package. | ai | |
| phantom-deps | phantom-dep:@lemonldap-ng/session-file | AI (phantom-deps): Optional backend dep; dynamically loaded, not statically imported. | ai | |
| phantom-deps | phantom-dep:@lemonldap-ng/session-ldap | AI (phantom-deps): Optional backend dep; dynamically loaded, not statically imported. | ai | |
| phantom-deps | phantom-dep:@lemonldap-ng/session-rest | AI (phantom-deps): Optional backend dep; dynamically loaded, not statically imported. | ai | |
| phantom-deps | phantom-dep:@lemonldap-ng/crypto | AI (phantom-deps): Same-org dep; likely loaded via dynamic require in session abstraction layer. | ai | |
| phantom-deps | phantom-dep:@lemonldap-ng/session-redis | AI (phantom-deps): Optional backend dep; dynamically loaded, not statically imported. | ai | |
| phantom-deps | phantom-dep:@lemonldap-ng/session-postgres | AI (phantom-deps): Optional backend dep; dynamically loaded, not statically imported. | ai | |
| phantom-deps | phantom-dep:ini | AI (phantom-deps): Config-file parsing dep; declared correctly, heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@lemonldap-ng/session-mysql | AI (phantom-deps): Optional backend dep; dynamically loaded, not statically imported. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.9.3 | 10 / 0 | |
| 0.9.1 | 10 / 0 | |
| 0.9.0 | 10 / 0 | |
| 0.8.0 | 10 / 0 | |
| 0.7.3 | 10 / 0 |
v0.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.