@cntrl-site/sdk
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 | large-new-source-files | AI (source-diff): New files are generated schema/dist build artifacts from added deps. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Growth from bundling new deps into dist output, not injected code. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Well-known UI libs added for legitimate feature (carousel/CSS-in-JS), matches package.json. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established SDK package with 230 versions; sparse README/keywords are cosmetic, not indicative of spam. | ai | |
| phantom-deps | phantom-dep:@splidejs/react-splide | AI (phantom-deps): Runtime dep used by consumers; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ts-node | AI (phantom-deps): ts-node is a runtime CLI dependency used in build/config context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/isomorphic-fetch | AI (phantom-deps): Type-only package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/ua-parser-js | AI (phantom-deps): Type-only package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:styled-jsx | AI (phantom-deps): Framework-scoped CSS-in-JS package; loaded by convention, not directly imported. | ai | |
| phantom-deps | phantom-dep:@types/ejs | AI (phantom-deps): Type-only package loaded by convention; not directly imported in source. | ai |
Versions (showing 72 of 72)
| Version | Deps | Published |
|---|---|---|
| 1.28.2 | 14 / 11 | |
| 1.28.1 | 14 / 11 | |
| 1.28.0 | 14 / 11 | |
| 1.27.2 | 14 / 11 | |
| 1.27.1 | 14 / 11 | |
| 1.27.0 | 14 / 11 | |
| 1.26.5 | 14 / 11 | |
| 1.26.4 | 14 / 11 | |
| 1.26.3 | 14 / 11 | |
| 1.26.2 | 14 / 11 | |
| 1.26.1 | 14 / 11 | |
| 1.26.0 | 14 / 11 | |
| 1.25.12 | 14 / 11 | |
| 1.25.11 | 14 / 11 | |
| 1.25.10 | 14 / 11 | |
| 1.25.9 | 14 / 11 | |
| 1.25.8 | 14 / 11 | |
| 1.25.7 | 14 / 11 | |
| 1.25.6 | 14 / 11 | |
| 1.25.5 | 14 / 11 | |
| 1.25.4 | 14 / 11 | |
| 1.25.3 | 14 / 11 | |
| 1.25.2 | 14 / 11 | |
| 1.25.1 | 14 / 11 | |
| 1.25.0 | 14 / 11 | |
| 1.24.6 | 15 / 16 | |
| 1.24.5 | 15 / 16 | |
| 1.24.4 | 15 / 16 | |
| 1.24.3 | 15 / 16 | |
| 1.24.2 | 15 / 15 | |
| 1.24.1 | 15 / 15 | |
| 1.24.0 | 15 / 12 | |
| 1.23.2 | 15 / 12 | |
| 1.23.0 | 15 / 12 | |
| 1.22.21 | 15 / 12 | |
| 1.22.20 | 15 / 12 | |
| 1.22.19 | 15 / 12 | |
| 1.22.18 | 15 / 12 | |
| 1.22.16 | 15 / 12 | |
| 1.22.15 | 15 / 12 | |
| 1.22.14 | 15 / 12 | |
| 1.22.13 | 15 / 12 | |
| 1.22.12 | 15 / 12 | |
| 1.22.11 | 15 / 12 | |
| 1.22.9 | 15 / 12 | |
| 1.22.8 | 15 / 12 | |
| 1.22.7 | 15 / 12 | |
| 1.22.6 | 15 / 12 | |
| 1.22.5 | 15 / 12 | |
| 1.22.4 | 15 / 12 | |
| 1.22.3 | 15 / 12 | |
| 1.22.2 | 15 / 12 | |
| 1.22.1 | 15 / 12 | |
| 1.22.0 | 15 / 12 | |
| 1.21.1 | 15 / 12 | |
| 1.21.0 | 15 / 12 | |
| 1.20.1 | 12 / 7 | |
| 1.20.0 | 12 / 7 | |
| 1.19.6 | 12 / 7 | |
| 1.19.5 | 12 / 7 | |
| 1.19.4 | 12 / 7 | |
| 1.19.3 | 12 / 7 | |
| 1.19.2 | 12 / 7 | |
| 1.19.1 | 12 / 7 | |
| 1.19.0 | 12 / 7 | |
| 1.17.0 | 12 / 7 | |
| 1.16.1 | 12 / 7 | |
| 1.16.0 | 12 / 7 | |
| 1.15.0 | 12 / 7 | |
| 1.14.0 | 12 / 7 | |
| 1.13.0 | 12 / 7 | |
| 1.12.3 | 12 / 7 |
v1.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.1
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-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.26.3
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 (arsenbatyuchok) on 2026-04-21, 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.25.10
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-03-18, 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.25.9
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-03-06, 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.25.7
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-02-25, 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.25.3
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-01-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.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.5
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 (sergokiko) on 2025-10-31, 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.24.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.3
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 (sergokiko) on 2025-10-13, 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.24.1
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 (sergokiko) on 2025-10-09, 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.24.0
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 2025-10-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.22.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.8
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 2025-05-07, 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.22.7
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 2025-05-07, 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.22.6
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 2025-05-06, 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.22.5
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 2025-05-01, 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.22.4
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 (arsenbatyuchok) than the most recent previously approved version (paula.uli) on 2025-05-01, but arsenbatyuchok 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.22.3
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 2025-05-01, 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.22.2
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 2025-04-30, 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.22.1
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 2025-04-30, 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.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
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 2025-04-25, 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.21.0
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 2025-04-25, 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.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.5
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 (arsenbatyuchok) on 2025-04-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.19.4
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 (arsenbatyuchok) than the most recent previously approved version (paula.uli) on 2024-12-17, but arsenbatyuchok 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.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
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 (arsenbatyuchok) on 2024-12-11, 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.17.0
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 (arsenbatyuchok) on 2024-12-04, 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.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
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 (arsenbatyuchok) on 2024-10-21, 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.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.