@ncds/ui-admin
nhn-commerce의 어드민 디자인 시스템입니다.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ncds/types-common | AI (dependencies): Internal org-scoped type package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@ncds/types-layout | AI (dependencies): Internal org-scoped type package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@atlaskit/pragmatic-drag-and-drop-react-accessibility | AI (phantom-deps): Declared as runtime dep but used indirectly via config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ncds/types-layout | AI (phantom-deps): Type-only dependency in same org scope; likely used only in .d.ts files, not directly imported in JS. | ai | |
| phantom-deps | phantom-dep:@ncds/types-common | AI (phantom-deps): Type-only dependency in same org scope; likely used only in .d.ts files, not directly imported in JS. | ai | |
| provenance | no-provenance | AI (provenance): Org-internal design system; provenance not configured, consistent across all 63 versions. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is explicitly declared in package.json dependencies; phantom-dep heuristic misfired. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.8.6 | 13 / 40 | |
| 1.8.5 | 13 / 40 | |
| 1.8.4 | 13 / 40 | |
| 1.8.3 | 13 / 40 | |
| 1.8.2 | 8 / 41 | |
| 1.8.1 | 8 / 39 | |
| 1.8.0 | 8 / 39 | |
| 1.7.0 | 8 / 38 | |
| 1.6.3 | 10 / 40 | |
| 1.6.0 | 10 / 40 | |
| 1.5.5 | 10 / 40 | |
| 1.5.4 | 10 / 40 | |
| 1.2.2 | 9 / 39 | |
| 1.1.2 | 9 / 39 | |
| 1.1.1 | 9 / 39 | |
| 1.1.0 | 9 / 39 |
v1.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.