@izara_project/izara-core-generate-service-code AGPL-3.0-or-later 52 versions

@izara_project/izara-core-generate-service-code

npm Repository Homepage

Code for locally generating per service files

52

Versions

AGPL-3.0-or-later

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

sventhebarbarian

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@izara_project/izara-shared	AI (phantom-deps): Same-org dependency; phantom-dep heuristic unreliable for intra-monorepo packages.	ai	2026/05/27
phantom-deps	phantom-dep:@izara_project/izara-middleware	AI (phantom-deps): Same-org dependency; phantom-dep heuristic unreliable for intra-monorepo packages.	ai	2026/05/27
phantom-deps	phantom-dep:@izara_project/izara-property-nodes	AI (phantom-deps): Same-org dependency; phantom-dep heuristic unreliable for intra-monorepo packages.	ai	2026/05/27
phantom-deps	phantom-dep:@izara_project/izara-core-library-core	AI (phantom-deps): Same-org dependency; phantom-dep heuristic unreliable for intra-monorepo packages.	ai	2026/05/27
phantom-deps	phantom-dep:@izara_project/izara-core-library-external-request	AI (phantom-deps): Same-org dependency; phantom-dep heuristic unreliable for intra-monorepo packages.	ai	2026/05/27
phantom-deps	phantom-dep:i	AI (phantom-deps): Utility dep used indirectly; stable false positive for this package.	ai	2026/05/27
phantom-deps	phantom-dep:npm	AI (phantom-deps): npm listed as dep for programmatic use in code-generation context; stable false positive.	ai	2026/05/27
phantom-deps	phantom-dep:object-hash	AI (phantom-deps): Utility dep used indirectly; stable false positive for this package.	ai	2026/05/27

Versions (showing 52 of 52)

Version	Deps	Published
1.0.52	8 / 1	2026-06-08
1.0.51	8 / 1	2026-06-04
1.0.50	8 / 1	2026-06-03
1.0.49	8 / 1	2026-06-02
1.0.48	8 / 1	2026-05-29
1.0.47	8 / 1	2026-05-29
1.0.46	8 / 1	2026-05-27
1.0.45	8 / 1	2026-05-25
1.0.44	8 / 1	2026-05-19
1.0.43	8 / 1	2026-05-18
1.0.42	8 / 1	2026-05-15
1.0.41	8 / 1	2026-05-14
1.0.40	8 / 1	2026-05-14
1.0.39	8 / 1	2026-05-04
1.0.38	8 / 1	2026-04-30
1.0.37	8 / 1	2026-04-29
1.0.36	8 / 1	2026-04-28
1.0.35	8 / 1	2026-04-26
1.0.34	8 / 1	2026-04-22
1.0.33	8 / 1	2026-04-21
1.0.32	8 / 1	2026-04-03
1.0.31	8 / 1	2026-04-02
1.0.30	8 / 1	2026-04-01
1.0.29	8 / 1	2026-03-25
1.0.28	8 / 1	2026-03-24
1.0.27	8 / 1	2026-03-23
1.0.26	8 / 1	2026-03-23
1.0.25	8 / 1	2026-03-20
1.0.24	8 / 1	2026-03-19
1.0.23	8 / 1	2026-03-18
1.0.22	8 / 1	2026-03-17
1.0.21	8 / 1	2026-03-16
1.0.20	8 / 1	2026-03-11
1.0.19	8 / 1	2026-03-09
1.0.18	8 / 1	2026-03-05
1.0.17	8 / 1	2026-03-04
1.0.16	8 / 1	2026-02-26
1.0.15	8 / 1	2026-02-25
1.0.14	8 / 1	2026-02-16
1.0.13	8 / 1	2026-02-13
1.0.12	8 / 1	2026-02-11
1.0.11	8 / 1	2026-02-06
1.0.10	8 / 1	2026-01-29
1.0.9	8 / 1	2026-01-28
1.0.8	8 / 1	2026-01-26
1.0.7	8 / 1	2026-01-09
1.0.6	8 / 1	2026-01-05
1.0.5	8 / 1	2025-12-25
1.0.4	8 / 1	2025-12-25
1.0.3	8 / 1	2025-12-19
1.0.2	8 / 1	2025-12-18
1.0.1	8 / 1	2025-12-16

v1.0.52

1 finding

LOW No provenance attestation provenance

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

v1.0.51

1 finding

LOW No provenance attestation provenance

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

v1.0.50

1 finding

LOW No provenance attestation provenance

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

v1.0.49

1 finding

LOW No provenance attestation provenance

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

v1.0.48

1 finding

LOW No provenance attestation provenance

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

v1.0.47

1 finding

LOW No provenance attestation provenance

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

v1.0.46

1 finding

LOW No provenance attestation provenance

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

v1.0.45

1 finding

LOW No provenance attestation provenance

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

v1.0.44

1 finding

LOW No provenance attestation provenance

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

v1.0.43

1 finding

LOW No provenance attestation provenance

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

v1.0.42

1 finding

LOW No provenance attestation provenance

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

v1.0.41

1 finding

LOW No provenance attestation provenance

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

v1.0.40

1 finding

LOW No provenance attestation provenance

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

v1.0.39

1 finding

LOW No provenance attestation provenance

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

v1.0.38

1 finding

LOW No provenance attestation provenance

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

v1.0.37

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

1 finding

LOW No provenance attestation provenance

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

v1.0.35

1 finding

LOW No provenance attestation provenance

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

v1.0.34

1 finding

LOW No provenance attestation provenance

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

v1.0.33

1 finding

LOW No provenance attestation provenance

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

v1.0.32

1 finding

LOW No provenance attestation provenance

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

v1.0.31

1 finding

LOW No provenance attestation provenance

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

v1.0.30

1 finding

LOW No provenance attestation provenance

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

v1.0.29

1 finding

LOW No provenance attestation provenance

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

v1.0.28

1 finding

LOW No provenance attestation provenance

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

v1.0.27

1 finding

LOW No provenance attestation provenance

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

v1.0.26

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

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

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

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

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

1 finding

LOW No provenance attestation provenance

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

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

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

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

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

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

v1.0.1

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.