@powerhousedao/network-admin AGPL-3.0-only 22 versions

@powerhousedao/network-admin

npm Repository Homepage

Network Admin package for Powerhouse

22

Versions

AGPL-3.0-only

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

acaldas.powerhousememo.devryanwolhuterprometheus-phcallme-tfroidliberuum

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@powerhousedao/vetra	AI (phantom-deps): Same-org monorepo dep; declared for transitive consumers, not directly imported in this package.	ai	2026/05/15
phantom-deps	phantom-dep:@powerhousedao/common	AI (phantom-deps): Same-org monorepo dep; declared for transitive consumers, not directly imported in this package.	ai	2026/05/15
phantom-deps	phantom-dep:@powerhousedao/builder-profile	AI (phantom-deps): Same-org monorepo dep; declared for transitive consumers, not directly imported in this package.	ai	2026/05/15
phantom-deps	phantom-dep:luxon	AI (phantom-deps): Utility dep likely used indirectly via config/type references; stable false positive for this package.	ai	2026/05/15
phantom-deps	phantom-dep:error	AI (phantom-deps): Utility dep referenced in config; stable false positive for this package.	ai	2026/05/15

Versions (showing 22 of 22)

Version	Deps	Published
1.2.0	17 / 37	2026-02-17
0.0.51	15 / 34	2025-12-09
0.0.50	15 / 34	2025-12-08
0.0.49	15 / 34	2025-11-27
0.0.48	15 / 34	2025-11-19
0.0.47	15 / 34	2025-11-19
0.0.46	15 / 34	2025-11-18
0.0.45	15 / 34	2025-11-18
0.0.44	15 / 34	2025-11-17
0.0.42	16 / 33	2025-11-12
0.0.41	16 / 33	2025-11-12
0.0.40	16 / 33	2025-11-12
0.0.39	16 / 33	2025-11-12
0.0.38	16 / 33	2025-11-12
0.0.37	14 / 29	2025-11-11
0.0.35	18 / 32	2025-11-06
0.0.34	14 / 29	2025-11-06
0.0.33	14 / 29	2025-11-05
0.0.32	14 / 29	2025-11-05
0.0.31	14 / 29	2025-11-05
0.0.30	14 / 29	2025-11-05
0.0.29	14 / 29	2025-11-05

v1.2.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.51

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

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

1 finding

LOW No provenance attestation provenance

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

v0.0.48

1 finding

LOW No provenance attestation provenance

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

v0.0.47

1 finding

LOW No provenance attestation provenance

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

v0.0.46

1 finding

LOW No provenance attestation provenance

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

v0.0.45

1 finding

LOW No provenance attestation provenance

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

v0.0.44

1 finding

LOW No provenance attestation provenance

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

v0.0.42

1 finding

LOW No provenance attestation provenance

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

v0.0.41

1 finding

LOW No provenance attestation provenance

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

v0.0.40

1 finding

LOW No provenance attestation provenance

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.38

1 finding

LOW No provenance attestation provenance

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

v0.0.37

1 finding

LOW No provenance attestation provenance

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

v0.0.35

1 finding

LOW No provenance attestation provenance

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

v0.0.34

1 finding

LOW No provenance attestation provenance

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

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. Consider requesting the maintainer enable provenance via CI/CD.

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.