← Home

@diia-inhouse/errors

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

Maintainers

diia-open-source

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@diia-inhouse/types AI (phantom-deps): Declared in both dependencies and peerDependencies; phantom-dep heuristic is a false positive for this package. ai
dependencies unvetted-dep:@diia-inhouse/types AI (dependencies): @diia-inhouse/types is a first-party sibling package in the same Diia ecosystem; unvetted status is expected and not a supply chain risk for this package. ai
provenance no-provenance AI (provenance): Established Diia open-source package with 690 days history and 23 versions; lack of provenance attestation is consistent across the ecosystem and not a risk signal here. ai

Versions (showing 51 of 61)

View all versions
Version Deps Published
2.2.11 1 / 17
2.2.10 1 / 17
2.2.9 1 / 17
2.2.8 1 / 17
2.2.7 1 / 17
2.2.6 1 / 17
2.2.5 1 / 17
2.2.4 1 / 17
2.2.3 1 / 17
2.2.2 1 / 17
2.2.1 1 / 17
2.2.0 1 / 17
2.1.21 1 / 17
2.1.20 1 / 17
2.1.19 1 / 17
2.1.18 1 / 17
2.1.17 1 / 17
2.1.16 1 / 17
2.1.15 1 / 17
2.1.14 1 / 17
2.1.13 1 / 17
2.1.12 1 / 17
2.1.11 1 / 17
2.1.10 1 / 17
2.1.9 1 / 17
2.1.8 1 / 17
2.1.7 1 / 17
2.1.6 1 / 17
2.1.5 1 / 17
2.1.4 1 / 17
2.1.3 1 / 17
2.1.2 1 / 17
2.1.1 1 / 17
2.1.0 1 / 17
1.18.24 1 / 17
1.18.23 1 / 17
1.18.21 1 / 17
1.18.20 1 / 17
1.18.19 1 / 17
1.18.18 1 / 17
1.18.17 1 / 17
1.18.16 1 / 17
1.18.15 1 / 17
1.18.14 1 / 17
1.18.13 1 / 17
1.18.12 1 / 17
1.18.11 1 / 17
1.18.10 1 / 17
1.18.9 1 / 17
1.18.8 1 / 17
1.18.7 1 / 17

v2.2.11

1 finding
INFO No provenance attestation provenance

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

v2.2.10

1 finding
INFO No provenance attestation provenance

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

v2.2.9

1 finding
INFO No provenance attestation provenance

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

v2.2.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.

v2.2.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.

v2.2.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.

v2.2.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.

v2.2.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.

v2.2.3

1 finding
INFO No provenance attestation provenance

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

v2.2.2

1 finding
INFO No provenance attestation provenance

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

v2.2.1

1 finding
INFO No provenance attestation provenance

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

v2.2.0

1 finding
INFO No provenance attestation provenance

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

v2.1.21

1 finding
INFO No provenance attestation provenance

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

v2.1.20

1 finding
INFO No provenance attestation provenance

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

v2.1.19

1 finding
INFO No provenance attestation provenance

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