@chipstcp/upyog-css
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:yarn | AI (phantom-deps): Build tooling mistakenly listed as runtime dep; not imported at runtime. | ai | |
| phantom-deps | phantom-dep:node-sass | AI (phantom-deps): SCSS build tool; not imported at runtime, stable false positive for this CSS package. | ai | |
| phantom-deps | phantom-dep:tailwindcss | AI (phantom-deps): CSS build tool; not imported at runtime, stable false positive for this CSS package. | ai | |
| phantom-deps | phantom-dep:postcss-scss | AI (phantom-deps): PostCSS build tool; not imported at runtime, stable false positive for this CSS package. | ai | |
| phantom-deps | phantom-dep:normalize.css | AI (phantom-deps): CSS dependency referenced in build config; stable false positive for this CSS package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.0.15 | 4 / 16 | |
| 1.0.14 | 4 / 16 | |
| 1.0.12 | 5 / 18 | |
| 1.0.11 | 5 / 18 | |
| 1.0.10 | 5 / 18 | |
| 1.0.9 | 5 / 18 | |
| 1.0.8 | 5 / 18 | |
| 1.0.7 | 5 / 18 | |
| 1.0.6 | 5 / 18 | |
| 1.0.5 | 5 / 18 | |
| 1.0.4 | 5 / 18 | |
| 1.0.3 | 5 / 18 | |
| 1.0.2 | 5 / 18 | |
| 1.0.1 | 5 / 18 | |
| 1.0.0 | 5 / 18 |
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
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 (saurabhsingh0001) than the most recent previously approved version (anou1234) on 2026-06-05, but saurabhsingh0001 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.12
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 (anou1234) than the most recent previously approved version (yawerali) on 2026-06-02, but anou1234 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.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.