@forestadmin/datasource-mongoose
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.13.4 | 2 / 1 | |
| 1.13.3 | 2 / 1 | |
| 1.13.2 | 2 / 1 | |
| 1.13.1 | 2 / 1 | |
| 1.13.0 | 2 / 1 | |
| 1.12.6 | 2 / 1 | |
| 1.12.5 | 2 / 1 | |
| 1.12.4 | 2 / 1 | |
| 1.12.3 | 2 / 1 |
v1.13.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.13.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.13.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.12.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.12.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.