power-assert-renderers
Power Assert output renderers
2
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
twada
Keywords
assertassertionpower-asserttesttesting
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): twada is a long-established publisher; the dormancy gap aligns with a legitimate architectural refactor replacing inline utilities with dedicated renderer sub-packages. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All 5 new deps are power-assert-renderer-* packages from the same twada ecosystem; this is a deliberate modularization, not suspicious dependency injection. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is explained by the browserify bundle now including the 5 new renderer sub-packages; the build script in package.json confirms this is intentional. | ai |
v0.1.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
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.