rooks
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @js-temporal/polyfill is a well-known temporal API polyfill; consistent with new temporal hooks. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is confirmed legitimate by SLSA/Sigstore attestation on this well-established package. | ai | |
| provenance | missing-githead | AI (provenance): Major version bump with build pipeline change; publisher identity is consistent with known maintainer imbhargav5. | ai | |
| source-diff | large-new-source-files | AI (source-diff): v7→v9 major version jump; 136 new files reflect individual hook modules being shipped separately, not injected code. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 9.8.0 | 4 / 102 | |
| 9.7.1 | 4 / 102 | |
| 9.7.0 | 5 / 102 | |
| 9.5.0 | 4 / 101 | |
| 9.4.2 | 4 / 101 | |
| 9.4.1 | 4 / 101 | |
| 9.4.0 | 4 / 101 | |
| 9.3.0 | 4 / 107 | |
| 9.2.0 | 4 / 107 | |
| 9.1.0 | 4 / 107 | |
| 9.0.2 | 4 / 107 | |
| 9.0.1 | 4 / 107 | |
| 9.0.0 | 4 / 106 | |
| 7.14.1 | 4 / 110 |
v9.7.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-23. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.7.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.5.0
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: imbhargav5.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.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: imbhargav5.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.1
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: imbhargav5.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.0
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: imbhargav5.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: imbhargav5.
v9.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: imbhargav5.
v9.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: imbhargav5.
v9.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: imbhargav5.
v9.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: imbhargav5.
v9.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: imbhargav5.