@trackunit/custom-field-components SEE LICENSE IN LICENSE.txt 29 versions

@trackunit/custom-field-components

npm Repository Homepage

The `@trackunit/custom-field-components` package contains UI components specifically for use with Custom Fields within [the Trackunit Manager platform](https://www.trackunit.com/services/manager/) and [`@trackunit/iris-app`](https://www.npmjs.com/package/

29

Versions

SEE LICENSE IN LICENSE.txt

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

sandbankemtandrupkla-trackunitmta-tutu-publisher

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:jest-fetch-mock	AI (phantom-deps): Testing dependency; referenced in config but not directly imported—stable pattern.	ai	2026/05/04
phantom-deps	phantom-dep:@testing-library/react	AI (phantom-deps): Testing framework loaded by convention; stable for this package.	ai	2026/05/04
phantom-deps	phantom-dep:@trackunit/react-test-setup	AI (phantom-deps): Same-org testing setup; stable pattern across versions.	ai	2026/05/04
bogus-package	bogus-package	AI (bogus-package): Established Trackunit monorepo component; README style is typical for internal library packages.	ai	2026/04/29
phantom-deps	phantom-dep:react-select	AI (phantom-deps): react-select is a declared runtime dep; phantom-dep heuristic is a false positive here.	ai	2026/04/29

Versions (showing 29 of 648)

Version	Deps	Published
1.3.156	14 / 0	2025-05-15
1.3.154	14 / 0	2025-05-15
1.3.151	14 / 0	2025-05-15
1.3.149	14 / 0	2025-05-14
1.3.148	14 / 0	2025-05-14
1.3.147	14 / 0	2025-05-14
1.3.146	14 / 0	2025-05-13
1.3.145	14 / 0	2025-05-13
1.3.144	14 / 0	2025-05-13
1.3.143	14 / 0	2025-05-13
1.3.141	14 / 0	2025-05-12
1.3.140	14 / 0	2025-05-09
1.3.139	14 / 0	2025-05-08
1.3.136	14 / 0	2025-05-07
1.3.135	14 / 0	2025-05-07
1.3.133	14 / 0	2025-05-06
1.3.132	14 / 0	2025-05-06
1.3.131	14 / 0	2025-05-06
1.3.130	14 / 0	2025-05-06
1.3.129	14 / 0	2025-05-05
1.3.127	14 / 0	2025-05-05
1.3.124	14 / 0	2025-05-01
1.3.123	14 / 0	2025-05-01
1.3.122	14 / 0	2025-04-30
1.3.121	14 / 0	2025-04-30
1.3.120	14 / 0	2025-04-29
1.3.119	14 / 0	2025-04-29
1.3.118	14 / 0	2025-04-28
1.3.115	14 / 0	2025-04-28

v1.3.156

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.154

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.151

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.149

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.148

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.147

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.146

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.145

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.144

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.143

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.141

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.140

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.139

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.136

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.135

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.133

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.132

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.131

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.130

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.129

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.127

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.124

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.123

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.122

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.121

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.120

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.119

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.118

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.115

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.