← Home

@egovernments/digit-ui-svg-components

npm Homepage
18
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

jagankumar-egovsathishp-egov

Keywords

digitsvgcomponentsegovDPG

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/main.js AI (source-diff): Webpack bundle output, not obfuscation; well-known lib code (prop-types) visible in sample. ai
publish-pattern new-deps-added AI (publish-pattern): react/react-dom already used as peerDeps in prior versions; not novel/unvetted. ai
phantom-deps phantom-dep:react-dom AI (phantom-deps): Bundled UMD lib; react-dom used transitively via build, common false positive pattern. ai

Versions (showing 18 of 18)

Version Deps Published
1.1.0 0 / 14
1.0.23 0 / 14
1.0.22 0 / 14
1.0.21 0 / 14
1.0.20 0 / 14
1.0.19 0 / 14
1.0.18 0 / 14
1.0.17 0 / 14
1.0.16 0 / 14
1.0.15 0 / 14
1.0.14 0 / 14
1.0.13 0 / 14
1.0.12 0 / 14
1.0.11 0 / 14
1.0.10 0 / 14
1.0.9 2 / 20
1.0.8 0 / 16
1.0.7 0 / 14

v1.0.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.9

3 findings
HIGH New obfuscated file: dist/main.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jagankumar-egov → nipunarora-egov (on 2024-05-14, known maintainer) provenance

This version was published by a different npm account (nipunarora-egov) than the most recent previously approved version (jagankumar-egov) on 2024-05-14, but nipunarora-egov 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.8

3 findings
HIGH New obfuscated file: dist/main.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: jagankumar-egov → nipunarora-egov (on 2024-05-14, known maintainer) provenance

This version was published by a different npm account (nipunarora-egov) than the most recent previously approved version (jagankumar-egov) on 2024-05-14, but nipunarora-egov 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.7

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.