@socialgouv/cdtn-utils
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 100 of 126)
| Version | Deps | Published |
|---|---|---|
| 4.237.0 | 0 / 12 | |
| 4.236.2 | 0 / 12 | |
| 4.235.0 | 0 / 12 | |
| 4.234.0 | 0 / 12 | |
| 4.233.1 | 0 / 12 | |
| 4.233.0 | 0 / 12 | |
| 4.232.0 | 0 / 12 | |
| 4.231.5 | 0 / 12 | |
| 4.231.4 | 0 / 12 | |
| 4.231.3 | 0 / 12 | |
| 4.231.1 | 0 / 12 | |
| 4.231.0 | 0 / 11 | |
| 4.230.2 | 0 / 11 | |
| 4.230.1 | 0 / 11 | |
| 4.230.0 | 0 / 11 | |
| 4.229.0 | 0 / 11 | |
| 4.228.3 | 0 / 11 | |
| 4.228.2 | 0 / 11 | |
| 4.228.0 | 0 / 11 | |
| 4.227.0 | 0 / 11 | |
| 4.226.0 | 0 / 11 | |
| 4.225.0 | 0 / 11 | |
| 4.224.0 | 0 / 11 | |
| 4.223.1 | 0 / 11 | |
| 4.223.0 | 0 / 11 | |
| 4.202.0 | 0 / 9 | |
| 4.201.0 | 0 / 9 | |
| 4.200.0 | 0 / 9 | |
| 4.199.0 | 0 / 9 | |
| 4.198.0 | 0 / 9 | |
| 4.197.0 | 0 / 9 | |
| 4.196.1 | 0 / 9 | |
| 4.196.0 | 0 / 9 | |
| 4.195.1 | 0 / 9 | |
| 4.195.0 | 0 / 9 | |
| 4.194.0 | 0 / 9 | |
| 4.193.2 | 0 / 9 | |
| 4.193.1 | 0 / 9 | |
| 4.193.0 | 0 / 9 | |
| 4.192.0 | 0 / 9 | |
| 4.191.0 | 0 / 9 | |
| 4.190.0 | 0 / 9 | |
| 4.189.0 | 0 / 9 | |
| 4.188.0 | 0 / 9 | |
| 4.187.2 | 0 / 9 | |
| 4.187.1 | 0 / 9 | |
| 4.187.0 | 0 / 9 | |
| 4.186.0 | 0 / 9 | |
| 4.185.0 | 0 / 9 | |
| 4.184.0 | 0 / 9 | |
| 4.183.2 | 0 / 9 | |
| 4.183.1 | 0 / 9 | |
| 4.183.0 | 0 / 9 | |
| 4.182.0 | 0 / 9 | |
| 4.181.0 | 0 / 9 | |
| 4.180.0 | 0 / 9 | |
| 4.179.1 | 0 / 9 | |
| 4.179.0 | 0 / 9 | |
| 4.178.0 | 0 / 9 | |
| 4.177.0 | 0 / 9 | |
| 4.176.0 | 0 / 9 | |
| 4.175.0 | 0 / 9 | |
| 4.174.0 | 0 / 9 | |
| 4.173.0 | 0 / 9 | |
| 4.172.3 | 0 / 9 | |
| 4.172.2 | 0 / 9 | |
| 4.172.0 | 0 / 9 | |
| 4.171.1 | 0 / 9 | |
| 4.170.1 | 0 / 9 | |
| 4.170.0 | 0 / 9 | |
| 4.169.0 | 0 / 9 | |
| 4.168.1 | 0 / 9 | |
| 4.168.0 | 0 / 9 | |
| 4.167.2 | 0 / 9 | |
| 4.167.1 | 0 / 9 | |
| 4.167.0 | 0 / 9 | |
| 4.166.0 | 0 / 9 | |
| 4.165.0 | 0 / 9 | |
| 4.164.2 | 0 / 9 | |
| 4.164.1 | 0 / 9 | |
| 4.164.0 | 0 / 9 | |
| 4.163.0 | 0 / 9 | |
| 4.162.0 | 0 / 9 | |
| 4.161.0 | 0 / 9 | |
| 4.160.0 | 0 / 9 | |
| 4.159.0 | 0 / 9 | |
| 4.158.1 | 0 / 9 | |
| 4.158.0 | 0 / 9 | |
| 4.157.0 | 0 / 9 | |
| 4.156.1 | 0 / 4 | |
| 4.156.0 | 0 / 4 | |
| 4.155.2 | 0 / 4 | |
| 4.155.1 | 0 / 4 | |
| 4.155.0 | 0 / 4 | |
| 4.154.0 | 0 / 4 | |
| 4.153.0 | 0 / 4 | |
| 4.152.0 | 0 / 4 | |
| 4.151.1 | 0 / 4 | |
| 4.151.0 | 0 / 4 | |
| 4.150.0 | 0 / 4 |
v4.237.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.236.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.235.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.234.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.233.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.233.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.179.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.179.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.178.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.177.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.176.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.175.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.174.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.173.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.172.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.172.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.172.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.171.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.170.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.170.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.169.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.168.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.168.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.167.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.167.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.167.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.166.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.165.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.164.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.164.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.164.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.163.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.162.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.161.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.160.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.159.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.158.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.158.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.157.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.156.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.156.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.155.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.155.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.155.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.154.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.153.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.152.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.151.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.151.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.150.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.