@powerhousedao/document-engineering
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:document-model | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-visually-hidden | AI (phantom-deps): Config-referenced UI dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-dialog | AI (phantom-deps): Config-referenced UI dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-separator | AI (phantom-deps): Declared dep used in config/stories, typical for UI component library. | ai | |
| phantom-deps | phantom-dep:remark-gfm | AI (phantom-deps): Declared dep used in config/stories, typical for UI component library. | ai | |
| phantom-deps | phantom-dep:date-fns-tz | AI (phantom-deps): Declared dep used in config/stories, typical for UI component library. | ai | |
| phantom-deps | phantom-dep:react-docgen | AI (phantom-deps): Declared dep used in config/stories, typical for UI component library. | ai | |
| phantom-deps | phantom-dep:@internationalized/date | AI (phantom-deps): Declared dep used in config/stories, typical for UI component library. | ai | |
| phantom-deps | phantom-dep:@zxcvbn-ts/matcher-pwned | AI (phantom-deps): Declared dep used in config/stories, typical for UI component library. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-dropdown-menu | AI (dependencies): @radix-ui/react-dropdown-menu is part of the widely-used Radix UI headless component library; no security concern. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-tooltip | AI (dependencies): @radix-ui/react-tooltip is part of the widely-used Radix UI headless component library; no security concern. | ai | |
| dependencies | unvetted-dep:react-confirm | AI (dependencies): react-confirm is a legitimate, well-known React confirmation dialog library; unvetted status reflects registry gap, not actual risk. | ai |
Versions (showing 51 of 58)
| Version | Deps | Published |
|---|---|---|
| 1.40.5 | 36 / 62 | |
| 1.40.4 | 36 / 61 | |
| 1.40.3 | 43 / 65 | |
| 1.40.2 | 43 / 65 | |
| 1.40.1 | 44 / 65 | |
| 1.40.0 | 44 / 65 | |
| 1.39.0 | 44 / 65 | |
| 1.38.0 | 45 / 67 | |
| 1.37.0 | 45 / 67 | |
| 1.36.0 | 45 / 67 | |
| 1.35.1 | 45 / 67 | |
| 1.35.0 | 45 / 67 | |
| 1.34.0 | 45 / 67 | |
| 1.33.0 | 44 / 66 | |
| 1.32.0 | 44 / 66 | |
| 1.31.0 | 44 / 66 | |
| 1.30.0 | 44 / 66 | |
| 1.29.0 | 44 / 66 | |
| 1.28.0 | 43 / 66 | |
| 1.27.0 | 42 / 66 | |
| 1.26.1 | 42 / 66 | |
| 1.26.0 | 42 / 66 | |
| 1.25.0 | 41 / 66 | |
| 1.24.0 | 40 / 65 | |
| 1.23.0 | 38 / 65 | |
| 1.22.0 | 38 / 65 | |
| 1.21.1 | 38 / 65 | |
| 1.21.0 | 38 / 65 | |
| 1.20.0 | 38 / 65 | |
| 1.19.0 | 38 / 65 | |
| 1.18.0 | 33 / 65 | |
| 1.17.0 | 33 / 65 | |
| 1.16.1 | 32 / 64 | |
| 1.16.0 | 32 / 64 | |
| 1.15.0 | 32 / 64 | |
| 1.14.0 | 32 / 64 | |
| 1.13.0 | 32 / 64 | |
| 1.12.0 | 32 / 64 | |
| 1.11.0 | 32 / 64 | |
| 1.10.0 | 32 / 64 | |
| 1.9.0 | 32 / 64 | |
| 1.8.1 | 32 / 64 | |
| 1.8.0 | 32 / 64 | |
| 1.7.0 | 32 / 53 | |
| 1.6.0 | 32 / 53 | |
| 1.5.0 | 32 / 53 | |
| 1.4.1 | 32 / 53 | |
| 1.4.0 | 32 / 53 | |
| 1.3.0 | 32 / 53 | |
| 1.2.2 | 32 / 53 | |
| 1.2.1 | 32 / 53 |
v1.40.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.