@powerhousedao/builder-profile
Builder profile document model
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; consistent with org-wide CI/CD adoption. | ai | |
| source-diff | obfuscated-file:dist/editors/builder-profile/components/ProfilePreview.js | AI (source-diff): Dist build output with long lines; code is readable JSX — not obfuscated. | ai | |
| phantom-deps | phantom-dep:graphql-tag | AI (phantom-deps): Declared dependency used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:error | AI (phantom-deps): Declared dependency used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@powerhousedao/common | AI (phantom-deps): Same-org scoped package likely used via re-exports; stable false positive. | ai | |
| phantom-deps | phantom-dep:@powerhousedao/vetra | AI (phantom-deps): Same-org scoped package likely used via re-exports; stable false positive. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): Declared dependency used indirectly; stable false positive for this package. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 1.0.8 | 13 / 37 | |
| 1.0.7 | 13 / 37 | |
| 1.0.6 | 13 / 37 | |
| 1.0.5 | 13 / 37 | |
| 1.0.4 | 13 / 37 | |
| 1.0.3 | 13 / 37 | |
| 1.0.2 | 13 / 37 | |
| 1.0.1 | 13 / 37 | |
| 1.0.0 | 13 / 37 | |
| 0.0.18 | 13 / 34 | |
| 0.0.17 | 13 / 34 | |
| 0.0.16 | 13 / 34 | |
| 0.0.15 | 13 / 34 | |
| 0.0.14 | 13 / 34 | |
| 0.0.13 | 13 / 34 | |
| 0.0.12 | 13 / 34 | |
| 0.0.11 | 13 / 34 | |
| 0.0.10 | 13 / 34 | |
| 0.0.9 | 12 / 34 | |
| 0.0.8 | 12 / 34 | |
| 0.0.7 | 12 / 34 | |
| 0.0.6 | 12 / 34 | |
| 0.0.5 | 10 / 34 | |
| 0.0.4 | 10 / 34 | |
| 0.0.3 | 9 / 34 |
v1.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-12. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.