@cntrl-site/components
Custom components for control editor and public websites.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@antfu/eslint-config | AI (phantom-deps): Dev/config-only tool declared as dep but never imported; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ts-node | AI (phantom-deps): Dev/config-only tool declared as dep but never imported; stable false positive for this package. | ai |
Versions (showing 51 of 57)
| Version | Deps | Published |
|---|---|---|
| 1.0.46 | 1 / 17 | |
| 1.0.45 | 1 / 17 | |
| 1.0.44 | 1 / 17 | |
| 1.0.43 | 1 / 17 | |
| 1.0.42 | 1 / 17 | |
| 1.0.41 | 1 / 17 | |
| 1.0.40 | 1 / 17 | |
| 1.0.39 | 1 / 17 | |
| 1.0.38 | 1 / 17 | |
| 1.0.37 | 1 / 17 | |
| 1.0.36 | 1 / 17 | |
| 1.0.35 | 1 / 17 | |
| 1.0.34 | 1 / 17 | |
| 1.0.33 | 1 / 17 | |
| 1.0.32 | 1 / 17 | |
| 1.0.31 | 1 / 17 | |
| 1.0.30 | 1 / 17 | |
| 1.0.29 | 1 / 17 | |
| 1.0.28 | 1 / 17 | |
| 1.0.27 | 1 / 17 | |
| 1.0.26 | 1 / 17 | |
| 1.0.24 | 1 / 17 | |
| 1.0.23 | 1 / 17 | |
| 1.0.22 | 1 / 17 | |
| 1.0.21 | 1 / 17 | |
| 1.0.20 | 1 / 17 | |
| 1.0.19 | 1 / 17 | |
| 1.0.18 | 1 / 17 | |
| 1.0.17 | 1 / 17 | |
| 1.0.16 | 1 / 17 | |
| 1.0.15 | 1 / 17 | |
| 1.0.14 | 1 / 17 | |
| 1.0.13 | 1 / 17 | |
| 1.0.12 | 1 / 17 | |
| 1.0.1 | 1 / 17 | |
| 0.1.34 | 1 / 17 | |
| 0.1.28 | 1 / 17 | |
| 0.1.27 | 1 / 17 | |
| 0.1.26 | 4 / 14 | |
| 0.1.24 | 4 / 14 | |
| 0.1.23 | 4 / 14 | |
| 0.1.22 | 4 / 14 | |
| 0.1.21 | 4 / 14 | |
| 0.1.20 | 4 / 14 | |
| 0.1.19 | 4 / 14 | |
| 0.1.18 | 4 / 14 | |
| 0.1.17 | 4 / 14 | |
| 0.1.16 | 4 / 14 | |
| 0.1.15 | 4 / 14 | |
| 0.1.5 | 4 / 14 | |
| 0.1.2 | 4 / 14 |
v1.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.45
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sergokiko) than the most recent previously approved version (paula.uli) on 2026-07-27, but sergokiko is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.44
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (paula.uli) than the most recent previously approved version (sergokiko) on 2026-07-23, but paula.uli is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.42
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sergokiko) than the most recent previously approved version (timurvnukov) on 2026-07-23, but sergokiko is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (timurvnukov) than the most recent previously approved version (paula.uli) on 2026-07-20, but timurvnukov is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.39
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (paula.uli) than the most recent previously approved version (sergokiko) on 2026-07-15, but paula.uli is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sergokiko) than the most recent previously approved version (timurvnukov) on 2026-07-14, but sergokiko is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (timurvnukov) than the most recent previously approved version (paula.uli) on 2026-07-14, but timurvnukov is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.33
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (paula.uli) than the most recent previously approved version (sergokiko) on 2026-07-13, but paula.uli is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sergokiko) than the most recent previously approved version (timurvnukov) on 2026-07-10, but sergokiko is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.29
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (timurvnukov) than the most recent previously approved version (paula.uli) on 2026-07-10, but timurvnukov is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.28
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (paula.uli) than the most recent previously approved version (timurvnukov) on 2026-07-09, but paula.uli is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (timurvnukov) than the most recent previously approved version (paula.uli) on 2026-07-08, but timurvnukov is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (paula.uli) than the most recent previously approved version (timurvnukov) on 2026-07-03, but paula.uli is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (timurvnukov) than the most recent previously approved version (paula.uli) on 2026-06-29, but timurvnukov is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.