@digital-realty/ix-app-logic
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Org-scoped package with 283 versions; no provenance is consistent across all releases. | ai | |
| dependencies | unvetted-dep:@adobe/lit-mobx | AI (dependencies): Legitimate Adobe-maintained LitElement+MobX binding; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:mobx-persist-store | AI (dependencies): Well-known MobX persistence library; no advisories and consistent use across this package's versions. | ai | |
| phantom-deps | phantom-dep:@digital-realty/theme | AI (phantom-deps): Same-org package; phantom-dep heuristic is a stable false positive for this monorepo-style library. | ai | |
| phantom-deps | phantom-dep:@digital-realty/ix-twlit | AI (phantom-deps): Same-org package; phantom-dep heuristic is a stable false positive for this monorepo-style library. | ai | |
| phantom-deps | phantom-dep:@adobe/lit-mobx | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 2.1.2 | 17 / 22 | |
| 2.1.1 | 17 / 22 | |
| 2.0.19 | 17 / 23 | |
| 2.0.9 | 17 / 23 | |
| 2.0.7 | 17 / 23 | |
| 2.0.6 | 17 / 23 | |
| 2.0.5 | 17 / 23 | |
| 2.0.4 | 17 / 23 | |
| 2.0.3 | 17 / 23 | |
| 2.0.2 | 17 / 23 | |
| 2.0.1 | 17 / 23 | |
| 1.2.22 | 16 / 23 | |
| 1.2.19 | 16 / 23 | |
| 1.2.18 | 16 / 23 | |
| 1.2.17 | 16 / 23 |
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.