@govtechsg/sgds-web-component
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers match listed contributors in package.json; legitimate team additions. | ai | |
| provenance | missing-githead | AI (provenance): Publish-env metadata gap, no behavioral change; diff shows no material changes. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Diff tool flagged count but version diff vs prior approved shows no material changes. | ai | |
| source-diff | obfuscated-file:components/Stepper/step.js | AI (source-diff): Bundled lit CSS template literal, long line not true obfuscation. | ai | |
| source-diff | obfuscated-file:react/components/Stepper/step.js | AI (source-diff): Same bundled CSS artifact in react wrapper build output. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 3.24.0 | 7 / 0 | |
| 3.23.0 | 7 / 0 | |
| 3.22.0 | 7 / 0 | |
| 3.21.0 | 7 / 0 | |
| 3.19.1 | 7 / 0 | |
| 3.19.0 | 7 / 0 | |
| 3.18.1 | 7 / 0 | |
| 3.18.0 | 7 / 0 | |
| 3.17.0 | 7 / 0 | |
| 3.16.0 | 7 / 0 | |
| 3.15.0 | 7 / 0 | |
| 3.14.0 | 7 / 0 | |
| 3.13.1 | 7 / 0 | |
| 3.13.0 | 7 / 0 | |
| 3.12.0 | 7 / 0 | |
| 3.11.0 | 7 / 0 | |
| 3.10.0 | 7 / 0 | |
| 3.9.0 | 7 / 0 | |
| 3.8.1 | 7 / 0 | |
| 3.8.0 | 7 / 0 | |
| 3.7.0 | 7 / 0 | |
| 3.6.4 | 7 / 0 | |
| 3.6.3 | 7 / 0 | |
| 3.6.2 | 7 / 0 | |
| 3.6.1 | 7 / 0 | |
| 3.6.0 | 7 / 0 | |
| 3.5.6 | 7 / 0 |
v3.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.0
4 findingsThis version was published by a different npm account than previous versions on 2026-07-06. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.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 (amandahive) than the most recent previously approved version (isomer.govtech) on 2026-05-19, but amandahive 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.
v3.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 (amandahive) than the most recent previously approved version (isomer.govtech) on 2026-05-13, but amandahive 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.
v3.18.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 (amandahive) than the most recent previously approved version (isomer.govtech) on 2026-05-04, but amandahive 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.
v3.15.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: isomer.govtech.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: isomer.govtech.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: isomer.govtech.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: isomer.govtech.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: isomer.govtech.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: isomer.govtech.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: isomer.govtech.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: isomer.govtech.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: isomer.govtech.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: isomer.govtech.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: isomer.govtech.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.