@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, 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 |
|---|---|---|---|---|
| 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 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.3.4 | 9 / 19 | |
| 1.3.2 | 9 / 19 | |
| 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 | |
| 1.1.6 | 9 / 20 | |
| 1.1.5 | 4 / 20 | |
| 1.1.4 | 5 / 18 | |
| 1.1.3 | 5 / 18 | |
| 1.0.30 | 5 / 18 | |
| 1.0.29 | 5 / 18 | |
| 1.0.28 | 5 / 18 | |
| 1.0.27 | 5 / 18 | |
| 1.0.26 | 5 / 18 | |
| 1.0.25 | 5 / 18 |
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.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.
v1.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.