@knime/styles
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): CSS tooling package; PostCSS deps are referenced in config files, not JS imports — expected pattern. | ai | |
| phantom-deps | phantom-dep:postcss-url | AI (phantom-deps): Same CSS config pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:postcss-import | AI (phantom-deps): Same CSS config pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:postcss-mixins | AI (phantom-deps): Same CSS config pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:modern-normalize | AI (phantom-deps): CSS normalization dep referenced in stylesheets, not JS imports — expected. | ai | |
| phantom-deps | phantom-dep:postcss-preset-env | AI (phantom-deps): Same CSS config pattern; stable false positive for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.15.1 | 6 / 1 | |
| 1.15.0 | 6 / 1 | |
| 1.14.3 | 6 / 1 | |
| 1.14.2 | 6 / 1 | |
| 1.14.1 | 6 / 1 | |
| 1.14.0 | 6 / 1 | |
| 1.13.0 | 6 / 1 | |
| 1.12.1 | 6 / 1 | |
| 1.12.0 | 6 / 1 | |
| 1.11.1 | 6 / 1 | |
| 1.11.0 | 6 / 1 | |
| 1.10.0 | 6 / 1 | |
| 1.9.0 | 6 / 1 | |
| 1.8.0 | 6 / 1 | |
| 1.7.0 | 6 / 1 | |
| 1.6.0 | 6 / 1 | |
| 1.5.0 | 6 / 1 |
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.