@webdeveric/utils
Just another collection of utilities.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 100 of 118)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 0 / 25 | |
| 1.1.0 | 0 / 25 | |
| 1.0.0 | 0 / 25 | |
| 0.83.3 | 0 / 25 | |
| 0.83.2 | 0 / 25 | |
| 0.83.1 | 0 / 24 | |
| 0.83.0 | 0 / 23 | |
| 0.82.0 | 0 / 23 | |
| 0.81.0 | 0 / 23 | |
| 0.80.1 | 0 / 23 | |
| 0.80.0 | 0 / 23 | |
| 0.79.0 | 0 / 23 | |
| 0.78.0 | 0 / 23 | |
| 0.77.0 | 0 / 23 | |
| 0.76.0 | 0 / 23 | |
| 0.75.0 | 0 / 23 | |
| 0.74.2 | 0 / 23 | |
| 0.74.1 | 0 / 23 | |
| 0.74.0 | 0 / 23 | |
| 0.73.0 | 0 / 23 | |
| 0.72.0 | 0 / 23 | |
| 0.71.2 | 0 / 23 | |
| 0.71.1 | 0 / 23 | |
| 0.71.0 | 0 / 23 | |
| 0.70.0 | 0 / 23 | |
| 0.69.0 | 0 / 23 | |
| 0.68.0 | 0 / 23 | |
| 0.67.0 | 0 / 23 | |
| 0.66.1 | 0 / 23 | |
| 0.66.0 | 0 / 23 | |
| 0.65.0 | 0 / 23 | |
| 0.64.0 | 0 / 23 | |
| 0.63.0 | 0 / 23 | |
| 0.62.0 | 0 / 23 | |
| 0.61.0 | 0 / 23 | |
| 0.60.0 | 0 / 23 | |
| 0.59.1 | 0 / 23 | |
| 0.59.0 | 0 / 23 | |
| 0.58.2 | 0 / 23 | |
| 0.58.1 | 0 / 23 | |
| 0.58.0 | 0 / 23 | |
| 0.57.0 | 0 / 23 | |
| 0.56.0 | 0 / 23 | |
| 0.55.0 | 0 / 23 | |
| 0.54.1 | 0 / 23 | |
| 0.54.0 | 0 / 23 | |
| 0.53.0 | 0 / 23 | |
| 0.52.0 | 0 / 23 | |
| 0.51.0 | 0 / 23 | |
| 0.50.0 | 0 / 23 | |
| 0.49.1 | 0 / 23 | |
| 0.49.0 | 0 / 23 | |
| 0.48.0 | 0 / 23 | |
| 0.47.0 | 0 / 23 | |
| 0.46.0 | 0 / 23 | |
| 0.45.1 | 0 / 23 | |
| 0.45.0 | 0 / 23 | |
| 0.44.0 | 0 / 23 | |
| 0.43.0 | 0 / 23 | |
| 0.42.0 | 0 / 23 | |
| 0.41.0 | 0 / 23 | |
| 0.40.0 | 0 / 17 | |
| 0.39.0 | 0 / 17 | |
| 0.38.0 | 2 / 19 | |
| 0.37.0 | 2 / 19 | |
| 0.36.0 | 2 / 19 | |
| 0.35.0 | 2 / 19 | |
| 0.34.0 | 2 / 19 | |
| 0.33.0 | 2 / 19 | |
| 0.32.0 | 2 / 19 | |
| 0.31.0 | 2 / 19 | |
| 0.30.0 | 2 / 19 | |
| 0.29.1 | 2 / 19 | |
| 0.29.0 | 2 / 19 | |
| 0.28.1 | 2 / 19 | |
| 0.28.0 | 2 / 19 | |
| 0.27.1 | 2 / 18 | |
| 0.27.0 | 2 / 18 | |
| 0.26.3 | 2 / 18 | |
| 0.26.2 | 2 / 18 | |
| 0.26.1 | 2 / 18 | |
| 0.26.0 | 2 / 18 | |
| 0.25.1 | 2 / 19 | |
| 0.25.0 | 2 / 18 | |
| 0.24.0 | 2 / 18 | |
| 0.23.0 | 2 / 24 | |
| 0.22.0 | 2 / 24 | |
| 0.21.0 | 2 / 24 | |
| 0.20.0 | 2 / 24 | |
| 0.19.0 | 2 / 24 | |
| 0.18.0 | 2 / 24 | |
| 0.17.1 | 3 / 24 | |
| 0.17.0 | 3 / 24 | |
| 0.16.0 | 3 / 24 | |
| 0.15.1 | 3 / 24 | |
| 0.15.0 | 3 / 24 | |
| 0.14.1 | 3 / 24 | |
| 0.14.0 | 3 / 23 | |
| 0.13.0 | 3 / 17 | |
| 0.12.0 | 3 / 17 |
v1.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.82.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.58.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.58.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.57.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.56.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.55.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.54.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.54.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.53.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.52.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.51.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.50.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.49.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.49.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.48.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.47.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.46.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.45.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.45.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.44.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.43.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.42.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.41.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.