dedent
A string tag that strips indentation from multi-line strings. ⬅️
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
Keywords
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): Dormancy consistent with maintainer transition; new publisher is well-established. | ai | |
| provenance | publisher-changed | AI (provenance): Documented maintainer transition from dmnd to joshuakgoldberg; stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): joshuakgoldberg is a known co-maintainer of dedent; stable. | ai | |
| source-diff | source-size-tripled | AI (source-diff): TypeScript rewrite with build tooling; expected size increase. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.7.2 | 0 / 43 | |
| 1.7.1 | 0 / 43 | |
| 1.7.0 | 0 / 42 | |
| 1.6.0 | 0 / 42 | |
| 0.7.0 | 0 / 6 |
v1.7.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: joshuakgoldberg.
This version was published by a different npm account than previous versions on 2025-12-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: joshuakgoldberg.
This version was published by a different npm account than previous versions on 2025-09-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
2 findingsThis version was published by a different npm account than previous versions on 2025-05-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.