@diia-inhouse/providers null 36 versions

@diia-inhouse/providers

npm Repository Homepage

common providers

36

Versions

null

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

diia-open-source

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@diia-inhouse/types	AI (dependencies): Same org scope (@diia-inhouse) as this package; internal ecosystem dependency, not a third-party unknown.	ai	2026/04/26
dependencies	unvetted-dep:@diia-inhouse/diia-queue	AI (dependencies): Same org scope (@diia-inhouse) as this package; internal ecosystem dependency, not a third-party unknown.	ai	2026/04/26
dependencies	unvetted-dep:@diia-inhouse/validators	AI (dependencies): Same org scope (@diia-inhouse) as this package; internal ecosystem dependency, not a third-party unknown.	ai	2026/04/26
dependencies	unvetted-dep:@diia-inhouse/diia-logger	AI (dependencies): Same org scope (@diia-inhouse) as this package; internal ecosystem dependency, not a third-party unknown.	ai	2026/04/26
phantom-deps	phantom-dep:@diia-inhouse/utils	AI (phantom-deps): Same-org package used as type-only or transitive import in a TypeScript project; phantom dep flag is a stable false positive for this package.	ai	2026/04/25
phantom-deps	phantom-dep:@diia-inhouse/diia-logger	AI (phantom-deps): Same-org package used as type-only or transitive import in a TypeScript project; phantom dep flag is a stable false positive for this package.	ai	2026/04/25

Versions (showing 36 of 36)

Version	Deps	Published
2.3.3	9 / 17	2026-06-06
2.3.2	9 / 17	2026-06-05
2.3.1	9 / 17	2026-06-03
2.3.0	9 / 17	2026-05-28
2.2.2	9 / 17	2026-05-27
2.2.1	9 / 17	2026-05-26
2.2.0	9 / 17	2026-05-25
1.39.31	9 / 16	2026-05-06
1.39.30	9 / 16	2026-05-03
1.39.27	9 / 16	2026-04-28
1.39.26	9 / 16	2026-04-28
1.39.25	9 / 16	2026-04-28
1.39.24	9 / 16	2026-04-27
1.39.23	9 / 16	2026-04-26
1.39.22	9 / 16	2026-04-25
1.39.21	9 / 16	2026-04-25
1.39.20	9 / 16	2026-04-23
1.39.19	9 / 16	2026-04-23
1.39.18	9 / 16	2026-04-20
1.39.17	9 / 16	2026-04-20
1.39.16	9 / 16	2026-04-16
1.39.15	9 / 16	2026-04-15
1.39.14	9 / 16	2026-04-13
1.39.13	9 / 16	2026-04-12
1.39.12	9 / 16	2026-04-12
1.39.11	9 / 16	2026-04-11
1.39.10	9 / 16	2026-04-10
1.39.9	9 / 16	2026-04-09
1.39.8	9 / 16	2026-04-04
1.39.7	9 / 16	2026-04-03
1.39.6	9 / 16	2026-03-29
1.39.5	9 / 16	2026-03-25
1.39.4	9 / 16	2026-03-19
1.39.3	9 / 16	2026-03-14
1.39.2	9 / 16	2026-03-12
1.39.0	9 / 16	2026-03-04

v2.3.3

1 finding

LOW No provenance attestation provenance

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

v2.3.2

1 finding

LOW No provenance attestation provenance

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

v2.3.1

1 finding

LOW No provenance attestation provenance

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

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.2

1 finding

LOW No provenance attestation provenance

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

v2.2.1

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v1.39.31

1 finding

LOW No provenance attestation provenance

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

v1.39.30

1 finding

LOW No provenance attestation provenance

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

v1.39.26

1 finding

LOW No provenance attestation provenance

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

v1.39.25

1 finding

LOW No provenance attestation provenance

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

v1.39.24

1 finding

LOW No provenance attestation provenance

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

v1.39.23

1 finding

LOW No provenance attestation provenance

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

v1.39.22

1 finding

LOW No provenance attestation provenance

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

v1.39.21

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

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

1 finding

LOW No provenance attestation provenance

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

v1.39.18

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

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

1 finding

LOW No provenance attestation provenance

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

v1.39.15

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

1 finding

LOW No provenance attestation provenance

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

v1.39.13

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

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

1 finding

LOW No provenance attestation provenance

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

v1.39.10

1 finding

LOW No provenance attestation provenance

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

v1.39.9

1 finding

LOW No provenance attestation provenance

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

v1.39.8

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

1 finding

LOW No provenance attestation provenance

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

v1.39.6

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

1 finding

LOW No provenance attestation provenance

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

v1.39.4

1 finding

LOW No provenance attestation provenance

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

v1.39.3

1 finding

LOW No provenance attestation provenance

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

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

v1.39.0

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.