time-fix-plugin
Fix startTime for webpack watcher
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Missing gitHead is consistent with a publish environment change during the 2018 maintainer transition; no other risk signals present. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from rem→egoist occurred in 2018; egoist is a highly trusted publisher (457 approved packages). This is a stable historical transition, not a compromise signal. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): egoist was added as maintainer in 2018 and is a well-established npm publisher with a strong track record. Legitimate historical transfer. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.0.7 | 0 / 3 | |
| 2.0.6 | 0 / 3 | |
| 2.0.5 | 0 / 3 | |
| 2.0.4 | 0 / 3 | |
| 2.0.3 | 0 / 3 | |
| 2.0.2 | 0 / 3 | |
| 2.0.1 | 0 / 3 | |
| 2.0.0 | 0 / 3 | |
| 1.0.0 | 0 / 2 |
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
2 findingsThis version was published by a different npm account than previous versions on 2019-05-15. 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.5
2 findingsThis version was published by a different npm account than previous versions on 2018-10-27. 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.4
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 2018-10-16. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
2 findingsThis version was published by a different npm account than previous versions on 2018-05-28. 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.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: egoist.
This version was published by a different npm account than previous versions on 2018-04-28. 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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.