@orion-js/dogs MIT 38 versions

@orion-js/dogs

npm

38

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

nicolaslopezjmario_dorochesi

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@orion-js/schema	AI (dependencies): Same-org monorepo sibling; stable pattern across all versions.	ai	2026/05/18
dependencies	unvetted-dep:@orion-js/helpers	AI (dependencies): Same-org monorepo sibling; stable pattern across all versions.	ai	2026/05/18
dependencies	unvetted-dep:@orion-js/services	AI (dependencies): Same-org monorepo sibling; stable pattern across all versions.	ai	2026/05/18
dependencies	unvetted-dep:@orion-js/typed-model	AI (dependencies): Same-org monorepo sibling; stable pattern across all versions.	ai	2026/05/18
typosquat	typosquat.levenshtein:cors	AI (typosquat): Scoped @orion-js monorepo package; Levenshtein match to 'cors' is coincidental, not a typosquat.	ai	2026/05/08
phantom-deps	phantom-dep:@orion-js/typed-model	AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic false positive for this monorepo package.	ai	2026/05/08
bogus-package	bogus-package	AI (bogus-package): Monorepo sub-package; missing description/repo in package.json is a metadata gap, not a spam indicator.	ai	2026/05/08
phantom-deps	phantom-dep:dataloader	AI (phantom-deps): dataloader is declared in dependencies; phantom-dep heuristic false positive for this package.	ai	2026/05/08
phantom-deps	phantom-dep:dot-object	AI (phantom-deps): dot-object is declared in dependencies; phantom-dep heuristic false positive for this package.	ai	2026/05/08

Versions (showing 38 of 38)

Version	Deps	Published
4.3.6	9 / 5	2026-05-29
4.3.5	9 / 5	2026-05-01
4.3.4	8 / 5	2026-04-10
4.3.3	8 / 5	2026-04-10
4.3.2	8 / 5	2026-04-10
4.3.1	8 / 5	2026-03-17
4.3.0	8 / 4	2026-02-28
4.2.10	8 / 5	2026-02-25
4.2.9	8 / 5	2026-02-18
4.2.8	8 / 5	2026-02-13
4.2.7	8 / 5	2026-02-04
4.2.6	8 / 5	2026-01-05
4.2.5	8 / 5	2026-01-05
4.2.4	8 / 5	2026-01-05
4.2.3	8 / 5	2026-01-05
4.2.1	8 / 5	2026-01-05
4.2.0	8 / 5	2026-01-05
4.1.12	8 / 5	2026-01-05
4.1.10	8 / 5	2025-12-08
4.1.9	8 / 5	2025-12-05
4.1.8	8 / 5	2025-10-21
4.1.7	8 / 5	2025-10-21
4.1.6	8 / 5	2025-10-21
4.1.5	8 / 5	2025-10-18
4.1.4	8 / 5	2025-10-17
4.1.3	8 / 5	2025-10-17
4.1.2	8 / 5	2025-10-17
4.1.1	8 / 5	2025-10-17
4.1.0	8 / 5	2025-10-17
4.0.34	8 / 5	2025-10-17
4.0.33	8 / 5	2025-10-16
4.0.32	8 / 5	2025-10-15
4.0.31	8 / 5	2025-10-15
4.0.30	8 / 5	2025-09-03
4.0.29	8 / 5	2025-08-29
4.0.28	8 / 5	2025-08-01
4.0.27	8 / 5	2025-06-10
4.0.26	8 / 5	2025-05-09

v4.3.6

1 finding

LOW No provenance attestation provenance

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

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

v4.3.4

1 finding

LOW No provenance attestation provenance

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

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

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

v4.3.1

1 finding

LOW No provenance attestation provenance

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

v4.3.0

1 finding

LOW No provenance attestation provenance

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

v4.2.10

1 finding

LOW No provenance attestation provenance

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

v4.2.9

1 finding

LOW No provenance attestation provenance

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

v4.2.8

1 finding

LOW No provenance attestation provenance

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

v4.2.7

1 finding

LOW No provenance attestation provenance

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

v4.2.6

1 finding

LOW No provenance attestation provenance

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

v4.2.5

1 finding

LOW No provenance attestation provenance

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

v4.2.4

1 finding

LOW No provenance attestation provenance

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

v4.2.3

1 finding

LOW No provenance attestation provenance

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

v4.2.1

1 finding

LOW No provenance attestation provenance

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

v4.2.0

1 finding

LOW No provenance attestation provenance

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

v4.1.12

1 finding

LOW No provenance attestation provenance

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

v4.1.10

1 finding

LOW No provenance attestation provenance

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

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

v4.1.8

1 finding

LOW No provenance attestation provenance

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

v4.1.7

1 finding

LOW No provenance attestation provenance

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

v4.1.6

1 finding

LOW No provenance attestation provenance

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

v4.1.5

1 finding

LOW No provenance attestation provenance

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

v4.1.4

1 finding

LOW No provenance attestation provenance

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

v4.1.3

1 finding

LOW No provenance attestation provenance

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

v4.1.2

1 finding

LOW No provenance attestation provenance

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

v4.1.1

1 finding

LOW No provenance attestation provenance

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

v4.1.0

1 finding

LOW No provenance attestation provenance

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

v4.0.34

1 finding

LOW No provenance attestation provenance

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

v4.0.33

1 finding

LOW No provenance attestation provenance

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

v4.0.32

1 finding

LOW No provenance attestation provenance

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

v4.0.31

1 finding

LOW No provenance attestation provenance

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

v4.0.30

1 finding

LOW No provenance attestation provenance

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

v4.0.29

1 finding

LOW No provenance attestation provenance

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

v4.0.28

1 finding

LOW No provenance attestation provenance

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

v4.0.27

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.

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