react-timer-mixin
TimerMixin provides timer functions for executing code in the future that are safely cleaned up when the component unmounts
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): spicyj and sophiebits are both npm accounts for Sophie Alpert (React core team); this is a documented account rename, not a hostile takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): sophiebits is Sophie Alpert's renamed npm account; addition reflects a legitimate account transition, not a new unknown party. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): spicyj removal is the other side of Sophie Alpert's account rename to sophiebits; no actual change in control. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by 2018 publish aligns with Sophie Alpert's npm account rename; no code changes introduced, consistent with routine maintenance. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.13.4 | 0 / 2 | |
| 0.13.3 | 0 / 2 | |
| 0.13.2 | 0 / 2 | |
| 0.13.1 | 0 / 2 | |
| 0.13.0 | 0 / 1 |
v0.13.4
2 findingsThis version was published by a different npm account than previous versions on 2018-07-17. 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.
v0.13.3
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 2015-09-09. This could indicate a legitimate maintainer transition or an account compromise.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.