@cityelectricalfactors/dds-components
Digital Design System themed components package for use across digital products.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are same-org scoped packages (@cityelectricalfactors/*); consistent with internal design system decomposition. | ai | |
| phantom-deps | phantom-dep:@playwright/test | AI (phantom-deps): Test tooling accidentally listed in dependencies; not a security risk for this package. | ai | |
| phantom-deps | phantom-dep:@vis.gl/react-google-maps | AI (phantom-deps): Maps component dep listed in dependencies but used in stories/config; not a security risk. | ai | |
| dependencies | unvetted-dep:@cityelectricalfactors/dds-design-tokens | AI (dependencies): Same-org sibling package in the CEF digital design system monorepo; stable false positive. | ai | |
| phantom-deps | phantom-dep:@cityelectricalfactors/dds-utils | AI (phantom-deps): Same-org monorepo sibling; indirect usage via bundled output is expected. | ai | |
| phantom-deps | phantom-dep:class-variance-authority | AI (phantom-deps): Referenced in config files; stable false positive for this build-tool pattern. | ai | |
| phantom-deps | phantom-dep:@cityelectricalfactors/dds-design-tokens | AI (phantom-deps): Same-org monorepo sibling; indirect usage via bundled output is expected. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 7.0.1 | 6 / 32 | |
| 7.0.0 | 6 / 31 | |
| 6.0.5 | 6 / 31 | |
| 6.0.4 | 6 / 31 | |
| 6.0.3 | 6 / 31 | |
| 6.0.2 | 6 / 31 | |
| 6.0.1 | 5 / 31 | |
| 6.0.0 | 5 / 31 | |
| 5.1.1 | 3 / 31 | |
| 5.1.0 | 3 / 31 | |
| 5.0.10 | 3 / 31 | |
| 5.0.9 | 3 / 31 | |
| 5.0.8 | 3 / 31 | |
| 5.0.7 | 3 / 31 | |
| 5.0.6 | 3 / 31 | |
| 5.0.5 | 3 / 31 | |
| 5.0.4 | 3 / 31 | |
| 5.0.3 | 3 / 31 | |
| 5.0.2 | 3 / 31 | |
| 5.0.1 | 3 / 31 | |
| 5.0.0 | 3 / 30 | |
| 4.1.1 | 3 / 30 | |
| 4.1.0 | 3 / 30 | |
| 4.0.1 | 3 / 30 | |
| 4.0.0 | 3 / 30 |
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.