@dugongjs/cli MIT 32 versions

@dugongjs/cli

npm

32

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

eriklysne

Keywords

dugongdugongjs

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	dormant-publish	AI (publish-pattern): Established org package with consistent publisher history; dormancy likely reflects development cadence, not takeover.	ai	2026/05/28
provenance	no-provenance	AI (provenance): No provenance across all 36 versions; stable pattern for this package.	ai	2026/05/14
npm-metadata	no-description	AI (npm-metadata): Early-stage monorepo CLI package; missing description is cosmetic, not a malice indicator.	ai	2026/05/14
phantom-deps	phantom-dep:@nestjs/common	AI (phantom-deps): Referenced in config files for scaffolding; stable false positive for this CLI package.	ai	2026/05/10
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped @dugongjs/cli is a CLI tool in the dugongjs ecosystem; Levenshtein match to 'joi' is a false positive.	ai	2026/05/10
phantom-deps	phantom-dep:@nestjs/platform-express	AI (phantom-deps): Referenced in config files for scaffolding; stable false positive for this CLI package.	ai	2026/05/10
phantom-deps	phantom-dep:@dugongjs/nestjs	AI (phantom-deps): Same-org dep referenced in templates/config; stable false positive for this CLI package.	ai	2026/05/10
phantom-deps	phantom-dep:rxjs	AI (phantom-deps): CLI tool referencing NestJS ecosystem deps in config/templates; not a real phantom dep issue.	ai	2026/05/10
phantom-deps	phantom-dep:@nestjs/core	AI (phantom-deps): Referenced in config files for scaffolding; stable false positive for this CLI package.	ai	2026/05/10

Versions (showing 32 of 32)

Version	Deps	Published
0.0.40	19 / 0	2026-05-26
0.0.39	19 / 0	2026-05-08
0.0.37	19 / 0	2026-05-05
0.0.36	19 / 0	2026-05-05
0.0.35	19 / 0	2026-05-05
0.0.33	19 / 0	2026-05-04
0.0.32	19 / 0	2026-05-03
0.0.31	19 / 0	2026-05-03
0.0.30	19 / 0	2026-05-02
0.0.29	19 / 0	2026-04-17
0.0.28	19 / 0	2026-04-16
0.0.27	19 / 0	2026-04-16
0.0.26	19 / 0	2026-04-10
0.0.25	19 / 0	2026-02-20
0.0.24	19 / 0	2026-02-10
0.0.23	19 / 0	2025-11-07
0.0.22	19 / 0	2025-09-17
0.0.21	16 / 0	2025-09-02
0.0.20	16 / 0	2025-08-29
0.0.16	16 / 0	2025-06-06
0.0.15	16 / 0	2025-06-06
0.0.14	16 / 0	2025-05-28
0.0.13	16 / 0	2025-05-28
0.0.12	16 / 0	2025-05-26
0.0.11	16 / 0	2025-05-26
0.0.10	16 / 0	2025-05-26
0.0.9	16 / 0	2025-05-26
0.0.8	16 / 0	2025-05-23
0.0.7	16 / 0	2025-05-16
0.0.6	16 / 0	2025-05-15
0.0.5	16 / 0	2025-05-13
0.0.4	16 / 0	2025-05-13

v0.0.40

1 finding

INFO No provenance attestation provenance

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

v0.0.39

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.

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

v0.0.36

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.

v0.0.35

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.

v0.0.33

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.

v0.0.32

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.

v0.0.31

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.

v0.0.30

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.

v0.0.29

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.

v0.0.28

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.

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

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

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

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

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

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

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

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

v0.0.16

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.

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

v0.0.14

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.

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

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

v0.0.11

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.

v0.0.10

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.

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

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

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

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

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

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