declastruct
Add declarative control to any resource constructs. Declare, plan, and apply within an observable pit-of-success.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
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 publisher with SLSA attestation; consistent with ehmpathy org automation pattern. | ai | |
| phantom-deps | phantom-dep:tsx | AI (phantom-deps): tsx is in devDependencies and also listed as runtime dep; phantom-dep is a false positive here. | ai | |
| phantom-deps | phantom-dep:uuid-fns | AI (phantom-deps): uuid-fns listed as runtime dep; phantom-dep heuristic fires but likely used indirectly. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Standard husky dev-only guard; only runs when .git exists, safe for consumers. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.9.1 | 11 / 28 | |
| 1.9.0 | 11 / 28 | |
| 1.8.0 | 11 / 28 | |
| 1.7.3 | 11 / 24 | |
| 1.7.2 | 11 / 24 | |
| 1.7.1 | 10 / 23 | |
| 1.7.0 | 10 / 23 | |
| 1.6.0 | 9 / 23 | |
| 1.5.2 | 9 / 23 | |
| 1.5.1 | 9 / 23 | |
| 1.5.0 | 9 / 23 | |
| 1.4.5 | 9 / 23 | |
| 1.4.4 | 9 / 23 | |
| 1.4.3 | 9 / 23 | |
| 1.4.2 | 9 / 23 | |
| 1.4.1 | 10 / 23 | |
| 1.4.0 | 9 / 33 | |
| 1.3.1 | 8 / 33 | |
| 1.3.0 | 8 / 24 | |
| 1.1.3 | 8 / 25 | |
| 1.1.0 | 8 / 25 | |
| 1.0.0 | 16 / 24 |
v1.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.3
2 findingsThis version was published by a different npm account than previous versions on 2025-12-16. 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.
v1.7.2
2 findingsThis version was published by a different npm account than previous versions on 2025-12-16. 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.
v1.7.1
2 findingsThis version was published by a different npm account than previous versions on 2025-12-14. 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.
v1.7.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-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.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
2 findingsScript: [ -d .git ] && npm run prepare:husky || exit 0
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
2 findingsScript: [ -d .git ] && npm run prepare:husky || exit 0
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.