@govtechsg/sgds-angular-component
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
isomer.govtechgyunikuchangds_ace_dltgdsbotgylskyryanoolaladyihoon90
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Sparse metadata is typical for early-version gov-tech library releases; not indicative of spam or malware. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Known gov-tech Angular component library; missing description is a metadata gap, not a risk signal. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.0.3 | 2 / 0 |
v0.0.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.