← Home

react-dates

npm Repository Homepage
16
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

ahuthairbnbengetienne_tripierkypanlencioniljharbmajapwmilesjnkinser21norataranoschleyfox

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:object.assign AI (phantom-deps): object.assign is a polyfill used via babel transform, not a direct import; stable false positive for this package. ai
phantom-deps phantom-dep:react-with-direction AI (phantom-deps): react-with-direction is a peer dep referenced in config; phantom-dep heuristic fires spuriously here. ai

Versions (showing 16 of 16)

Version Deps Published
21.8.0 15 / 61
21.7.2 15 / 61
21.7.1 15 / 61
21.7.0 15 / 61
21.6.0 15 / 61
21.5.1 15 / 61
21.5.0 15 / 61
21.4.0 15 / 61
21.3.2 15 / 61
21.3.1 15 / 61
21.3.0 15 / 61
21.2.1 15 / 61
21.2.0 15 / 61
21.1.0 15 / 61
21.0.1 15 / 61
21.0.0 15 / 61

v21.7.2

1 finding
LOW No provenance attestation provenance

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

v21.7.1

1 finding
LOW No provenance attestation provenance

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

v21.7.0

1 finding
LOW No provenance attestation provenance

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

v21.6.0

1 finding
LOW No provenance attestation provenance

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

v21.5.1

2 findings
MEDIUM Publisher changed: majapw → kypan (on 2019-12-10, unremoved on npm for 2419d) provenance

This version was published by a different npm account (kypan) than the most recent previously approved version (majapw) on 2019-12-10. It has since remained available on npm for 2419 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v21.5.0

2 findings
MEDIUM Publisher changed: noratarano → kypan (on 2019-11-14, unremoved on npm for 2446d) provenance

This version was published by a different npm account (kypan) than the most recent previously approved version (noratarano) on 2019-11-14. It has since remained available on npm for 2446 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v21.4.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: noratarano → majapw (on 2019-11-12, known maintainer) provenance

This version was published by a different npm account (majapw) than the most recent previously approved version (noratarano) on 2019-11-12, but majapw 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.

v21.3.2

1 finding
LOW No provenance attestation provenance

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

v21.3.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: majapw → noratarano (on 2019-10-22, known maintainer) provenance

This version was published by a different npm account (noratarano) than the most recent previously approved version (majapw) on 2019-10-22, but noratarano 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.

v21.3.0

1 finding
LOW No provenance attestation provenance

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

v21.2.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: noratarano → majapw (on 2019-10-12, known maintainer) provenance

This version was published by a different npm account (majapw) than the most recent previously approved version (noratarano) on 2019-10-12, but majapw 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.

v21.2.0

1 finding
LOW No provenance attestation provenance

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

v21.1.0

1 finding
LOW No provenance attestation provenance

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

v21.0.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.

v21.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.