@digital-realty/ix-time
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@adobe/lit-mobx | AI (dependencies): Adobe-maintained LitElement+MobX binding; well-known library, stable for this package. | ai | |
| dependencies | unvetted-dep:mobx-persist-store | AI (dependencies): Established MobX persistence library; no known advisories, stable for this package. | ai | |
| dependencies | unvetted-dep:@web/test-runner-commands | AI (dependencies): Part of the @web/test-runner ecosystem by Modern Web; test utility, stable for this package. | ai | |
| phantom-deps | phantom-dep:mobx-persist-store | AI (phantom-deps): Peer dependency pattern in web component library; stable false positive. | ai | |
| phantom-deps | phantom-dep:mobx | AI (phantom-deps): Peer dependency pattern in web component library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@web/test-runner-commands | AI (phantom-deps): Test tooling dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@vaadin/time-picker | AI (phantom-deps): Peer dependency pattern in web component library; stable false positive. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Peer dependency pattern in web component library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@adobe/lit-mobx | AI (phantom-deps): Peer dependency pattern in web component library; stable false positive. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.3.1 | 9 / 20 | |
| 1.2.12 | 9 / 20 | |
| 1.2.4 | 9 / 20 | |
| 1.2.3 | 9 / 20 | |
| 1.2.2 | 9 / 20 | |
| 1.2.1 | 9 / 20 | |
| 1.1.8 | 9 / 20 | |
| 1.1.7 | 9 / 20 |
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.