@digital-realty/ix-phone-input
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.4.5 | 6 / 24 | |
| 2.4.3 | 6 / 24 | |
| 2.4.2 | 6 / 25 | |
| 2.4.1 | 6 / 25 | |
| 2.3.12 | 6 / 25 | |
| 2.3.4 | 6 / 25 | |
| 2.3.3 | 6 / 25 | |
| 2.3.2 | 6 / 25 | |
| 2.3.1 | 6 / 25 | |
| 2.2.12 | 6 / 25 | |
| 2.2.11 | 6 / 25 | |
| 2.2.10 | 6 / 25 | |
| 2.2.9 | 6 / 25 | |
| 2.2.8 | 6 / 25 | |
| 2.2.7 | 6 / 25 | |
| 2.2.6 | 6 / 25 | |
| 2.2.5 | 6 / 24 | |
| 2.2.4 | 6 / 24 | |
| 2.2.3 | 6 / 24 | |
| 2.1.33 | 6 / 24 | |
| 2.1.32 | 6 / 24 |
v2.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nicholasnewlands) than the most recent previously approved version (dlr-pi-devops) on 2024-11-14, but nicholasnewlands is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.2.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nicholasnewlands) than the most recent previously approved version (dlr-pi-devops) on 2024-10-08, but nicholasnewlands is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.