← Home

@djb25/digit-ui-module-commonpt

Digit PT Light weight Module

9
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

djb25

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@djb25/digit-ui-react-components AI (dependencies): Sibling scoped package from the same publisher namespace (@djb25); expected dependency for a modular UI library in this ecosystem. ai
dependencies unvetted-dep:microbundle-crl AI (dependencies): microbundle-crl is a build tool used only in build scripts; not a runtime risk for consumers of this package. ai
dependencies unvetted-dep:react-query AI (dependencies): react-query is a well-known, widely-used data-fetching library; unvetted status reflects pipeline gap, not a real risk for this package. ai
provenance no-provenance AI (provenance): No provenance is common (~88% of npm packages); no other indicators of supply chain compromise for this package. ai
phantom-deps phantom-dep:react-dom AI (phantom-deps): react-dom is declared as a dependency and referenced in config/build files; not a security concern for this UI module package. ai
phantom-deps phantom-dep:microbundle-crl AI (phantom-deps): microbundle-crl is a build tool referenced in scripts/config; phantom-dep finding is expected for build tooling. ai
phantom-deps phantom-dep:lodash.merge AI (phantom-deps): lodash.merge declared but used via config; standard packaging pattern, no security risk. ai

Versions (showing 9 of 9)

Version Deps Published
1.0.8 9 / 0
1.0.7 9 / 0
1.0.6 9 / 0
1.0.5 9 / 0
1.0.4 9 / 0
1.0.3 9 / 0
1.0.2 9 / 0
1.0.1 9 / 0
1.0.0 9 / 0

v1.0.8

1 finding
INFO No provenance attestation provenance

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

v1.0.7

1 finding
INFO No provenance attestation provenance

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

v1.0.6

1 finding
INFO No provenance attestation provenance

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

v1.0.5

1 finding
INFO No provenance attestation provenance

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

v1.0.4

1 finding
INFO No provenance attestation provenance

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

v1.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.

v1.0.2

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.