react-document-title
A declarative, nested, stateful document.title for React
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): gaearon (Dan Abramov) is the original author of react-document-title; the publisher change reflects a legitimate ownership reclaim from a temporary maintainer. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): prop-types was added in April 2017 as the canonical migration when React 15.5 split PropTypes into a standalone package. This is expected and benign for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): gaearon is Dan Abramov, a well-known React core team member and creator of Redux. The spam flag is a false positive for this high-profile, legitimate publisher. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.0.3 | 2 / 9 | |
| 2.0.2 | 1 / 5 | |
| 2.0.1 | 1 / 5 | |
| 2.0.0 | 1 / 5 | |
| 1.0.4 | 1 / 5 | |
| 1.0.3 | 1 / 5 | |
| 1.0.2 | 1 / 5 | |
| 1.0.1 | 1 / 5 | |
| 0.1.3 | 0 / 5 | |
| 0.1.2 | 0 / 5 | |
| 0.1.1 | 0 / 0 | |
| 0.1.0 | 0 / 0 |
v2.0.3
2 findingsThis version was published by a different npm account than previous versions on 2017-04-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-06-10. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gaearon.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.