ts-dedent
TypeScript package which smartly trims and strips indentation from multi-line strings
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 | missing-githead | AI (provenance): Publish moved to GitHub Actions with SLSA provenance; gitHead absence is expected for CI-published packages. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): tamino-martinius is the package author per package.json and GitHub repo; switched from alt account next-model. Legitimate ownership consolidation. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from next-model to tamino-martinius is the same developer consolidating accounts; confirmed by author field and repo URL. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): tamino-martinius is the original author; adding their primary account is expected. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): next-model was an alternate account of the same author; removal is part of legitimate consolidation. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase from including src/ directory alongside dist/; no payload concern for this simple utility. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.3.0 | 0 / 6 | |
| 2.2.0 | 0 / 8 | |
| 2.1.1 | 0 / 8 | |
| 2.1.0 | 0 / 8 | |
| 2.0.0 | 0 / 8 | |
| 1.2.0 | 0 / 8 | |
| 1.1.1 | 0 / 8 | |
| 1.1.0 | 0 / 8 | |
| 1.0.0 | 0 / 8 |
v2.3.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: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-06-10. This could indicate a legitimate maintainer transition or an account compromise.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
3 findingsAll previous maintainers (next-model) were replaced by new maintainers (tamino-martinius). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2020-01-25. 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.1.0
1 findingPackage 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.