@digital-realty/ix-account-switcher
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established org package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 84 of 84)
| Version | Deps | Published |
|---|---|---|
| 1.3.9 | 11 / 18 | |
| 1.3.7 | 11 / 19 | |
| 1.3.6 | 11 / 19 | |
| 1.3.5 | 11 / 19 | |
| 1.3.4 | 11 / 19 | |
| 1.3.3 | 11 / 19 | |
| 1.3.2 | 11 / 19 | |
| 1.3.1 | 11 / 19 | |
| 1.2.25 | 11 / 21 | |
| 1.2.17 | 11 / 21 | |
| 1.2.16 | 11 / 21 | |
| 1.2.15 | 11 / 21 | |
| 1.2.14 | 11 / 21 | |
| 1.2.13 | 11 / 21 | |
| 1.2.12 | 11 / 21 | |
| 1.2.11 | 11 / 21 | |
| 1.2.10 | 11 / 21 | |
| 1.2.9 | 11 / 21 | |
| 1.2.8 | 11 / 21 | |
| 1.2.7 | 11 / 21 | |
| 1.2.6 | 11 / 21 | |
| 1.2.5 | 11 / 21 | |
| 1.2.4 | 11 / 21 | |
| 1.2.3 | 11 / 21 | |
| 1.2.2 | 11 / 21 | |
| 1.2.1 | 11 / 21 | |
| 1.1.33 | 9 / 21 | |
| 1.1.32 | 9 / 21 | |
| 1.1.31 | 9 / 21 | |
| 1.1.30 | 9 / 21 | |
| 1.1.29 | 9 / 21 | |
| 1.1.28 | 9 / 21 | |
| 1.1.27 | 9 / 21 | |
| 1.1.26 | 9 / 21 | |
| 1.1.25 | 9 / 21 | |
| 1.1.24 | 9 / 21 | |
| 1.1.23 | 9 / 21 | |
| 1.1.22 | 9 / 21 | |
| 1.1.21 | 9 / 21 | |
| 1.1.20 | 9 / 21 | |
| 1.1.19 | 9 / 21 | |
| 1.1.18 | 9 / 21 | |
| 1.1.17 | 9 / 21 | |
| 1.1.16 | 9 / 21 | |
| 1.1.15 | 11 / 21 | |
| 1.1.14 | 11 / 20 | |
| 1.1.13 | 11 / 20 | |
| 1.1.12 | 11 / 20 | |
| 1.1.11 | 11 / 20 | |
| 1.1.10 | 11 / 20 | |
| 1.1.9 | 11 / 20 | |
| 1.1.8 | 11 / 20 | |
| 1.1.7 | 11 / 20 | |
| 1.1.6 | 11 / 20 | |
| 1.1.5 | 11 / 20 | |
| 1.1.4 | 11 / 20 | |
| 1.1.3 | 11 / 20 | |
| 1.0.29 | 11 / 20 | |
| 1.0.28 | 11 / 20 | |
| 1.0.27 | 11 / 20 | |
| 1.0.26 | 11 / 20 | |
| 1.0.25 | 11 / 20 | |
| 1.0.24 | 11 / 20 | |
| 1.0.23 | 11 / 20 | |
| 1.0.21 | 11 / 20 | |
| 1.0.20 | 11 / 20 | |
| 1.0.19 | 11 / 20 | |
| 1.0.18 | 11 / 20 | |
| 1.0.17 | 11 / 20 | |
| 1.0.16 | 11 / 20 | |
| 1.0.15 | 11 / 20 | |
| 1.0.14 | 11 / 20 | |
| 1.0.13 | 11 / 20 | |
| 1.0.12 | 11 / 20 | |
| 1.0.11 | 11 / 20 | |
| 1.0.10 | 11 / 20 | |
| 1.0.9 | 11 / 20 | |
| 1.0.8 | 11 / 20 | |
| 1.0.7 | 11 / 20 | |
| 1.0.6 | 11 / 20 | |
| 1.0.5 | 11 / 20 | |
| 1.0.4 | 11 / 20 | |
| 1.0.3 | 11 / 20 | |
| 1.0.1 | 11 / 20 |
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
2 findings[Accepted risk] Package 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.
v1.1.3
2 findings[Accepted risk] Package 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.
v1.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dlr-pi-devops) than the most recent previously approved version (nicholasnewlands) on 2024-05-16, but dlr-pi-devops 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.
v1.0.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dlr-pi-devops) than the most recent previously approved version (nicholasnewlands) on 2024-05-15, but dlr-pi-devops 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.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.