@enonic-types/lib-mail
Type definitions for lib-mail.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@enonic-types/core | AI (dependencies): Sibling type-definition package from the same enonic/xp repo; no runtime code, stable pattern across versions. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 7.16.4 | 1 / 0 | |
| 7.16.3 | 1 / 0 | |
| 7.16.2 | 1 / 0 | |
| 7.16.1 | 1 / 0 | |
| 7.16.0 | 1 / 0 | |
| 7.15.4 | 1 / 0 | |
| 7.15.3 | 1 / 0 | |
| 7.15.2 | 1 / 0 |
v7.16.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.16.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.16.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.