← Home

@date-vir/duration

npm Repository Homepage

Durations units an utils for date-vir.

8
Versions
(MIT or CC0 1.0)
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

electrovir

Keywords

durationdateutiltime

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
license uncommon-license:CC0 1.0 AI (license): License is dual (MIT or CC0 1.0); both are well-known permissive licenses. CC0 flag is a false positive for this package. ai
phantom-deps phantom-dep:@types/luxon AI (phantom-deps): @types/luxon is a TypeScript type declaration package legitimately included as a runtime dep for type distribution; common pattern for TS libraries. ai

Versions (showing 8 of 8)

Version Deps Published
8.3.2 4 / 10
8.3.1 4 / 10
8.3.0 4 / 10
8.2.1 4 / 10
8.2.0 4 / 10
8.1.1 4 / 10
8.1.0 3 / 11
8.0.0 3 / 11

v8.3.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.

v8.3.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.

v8.3.0

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.

v8.2.1

1 finding
LOW No provenance attestation provenance

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

v8.2.0

1 finding
LOW No provenance attestation provenance

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

v8.1.1

1 finding
LOW No provenance attestation provenance

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

v8.1.0

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.

v8.0.0

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.