← Home

@digital-realty/ix-date-next

npm
10
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

dlr-pi-devopsnicholasnewlandsmarcha-dlralex-sommerville

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@adobe/lit-mobx AI (dependencies): Legitimate Adobe-maintained LitElement+MobX binding; stable known library. ai
dependencies unvetted-dep:mobx-persist-store AI (dependencies): Well-known MobX persistence library; no malicious indicators. ai
phantom-deps phantom-dep:sinon AI (phantom-deps): sinon is a test utility accidentally listed in dependencies; not imported at runtime, no security risk. ai
phantom-deps phantom-dep:unbzip2-stream AI (phantom-deps): unbzip2-stream appears to be an indirect/config-referenced dep, not a security concern for this web component package. ai

Versions (showing 10 of 10)

Version Deps Published
1.2.1 8 / 21
1.1.16 8 / 16
1.1.8 8 / 16
1.1.7 8 / 16
1.1.6 8 / 16
1.1.5 8 / 16
1.1.4 8 / 16
1.1.3 8 / 16
1.1.2 7 / 16
1.1.1 7 / 16

v1.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.