@jobber/hooks
Shared hooks for components in Atlantis.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/isObjectLike-cjs.js | AI (source-diff): Rollup-bundled lodash utility; no actual network calls or dynamic exec — standard CJS bundle boilerplate. | ai | |
| source-diff | net-exec-file:dist/isObjectLike-es.js | AI (source-diff): Rollup-bundled lodash utility (ESM variant); same false-positive pattern as CJS counterpart. | ai | |
| source-diff | net-exec-file:dist/useResizeObserver-cjs.js | AI (source-diff): Bundled resize-observer-polyfill; declared dep, no actual network/exec payload. | ai | |
| source-diff | net-exec-file:dist/useResizeObserver-es.js | AI (source-diff): Bundled resize-observer-polyfill (ESM variant); same false-positive pattern. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Monorepo build artifact; lodash is a declared runtime dep, phantom detection is a false positive. | ai | |
| phantom-deps | phantom-dep:resize-observer-polyfill | AI (phantom-deps): Declared runtime dep; phantom detection false positive in bundled output. | ai | |
| phantom-deps | phantom-dep:ts-xor | AI (phantom-deps): Declared runtime dep; phantom detection false positive in bundled output. | ai | |
| phantom-deps | phantom-dep:tiny-invariant | AI (phantom-deps): Declared runtime dep; phantom detection false positive in bundled output. | ai | |
| phantom-deps | phantom-dep:use-resize-observer | AI (phantom-deps): Declared runtime dep; phantom detection false positive in bundled output. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 2.20.0 | 6 / 13 | |
| 2.19.4 | 6 / 13 | |
| 2.19.3 | 6 / 6 | |
| 2.19.2 | 6 / 6 | |
| 2.19.1 | 6 / 6 | |
| 2.19.0 | 6 / 6 | |
| 2.18.1 | 6 / 8 | |
| 2.18.0 | 6 / 8 | |
| 2.17.4 | 6 / 8 | |
| 2.17.3 | 6 / 8 | |
| 2.17.2 | 6 / 8 | |
| 2.17.1 | 6 / 8 | |
| 2.17.0 | 6 / 8 | |
| 2.16.0 | 5 / 8 | |
| 2.15.0 | 4 / 8 | |
| 2.14.0 | 4 / 8 | |
| 2.13.1 | 4 / 8 | |
| 2.13.0 | 5 / 9 | |
| 2.12.4 | 5 / 9 | |
| 2.12.3 | 5 / 9 | |
| 2.12.1 | 5 / 9 | |
| 2.11.1 | 5 / 13 | |
| 2.11.0 | 5 / 13 | |
| 2.10.2 | 5 / 13 | |
| 2.10.1 | 5 / 13 | |
| 2.10.0 | 5 / 13 | |
| 2.9.8 | 5 / 13 | |
| 2.9.7 | 5 / 13 | |
| 2.9.6 | 5 / 13 |
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.