@tailor-platform/erp-kit
Opinionated ERP toolkit for building business applications on Tailor Platform
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): CLI tool bundling templates and dist output; large file count is structural, not injected payload. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase matches addition of CLI dist bundle and scaffold templates, not obfuscated code. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Fires only in integration test file; spreading process.env for test subprocess env is standard and not a production risk. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP is 127.0.0.1 (localhost) used for a local mock server — not an exfiltration endpoint. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 0.34.0 | 15 / 12 | |
| 0.33.0 | 15 / 12 | |
| 0.32.0 | 13 / 11 | |
| 0.31.0 | 13 / 11 | |
| 0.30.0 | 13 / 11 | |
| 0.29.0 | 13 / 11 | |
| 0.28.1 | 13 / 11 | |
| 0.28.0 | 13 / 11 | |
| 0.27.0 | 13 / 11 | |
| 0.26.0 | 13 / 11 | |
| 0.25.0 | 13 / 11 | |
| 0.24.0 | 13 / 11 | |
| 0.23.0 | 13 / 11 | |
| 0.22.0 | 13 / 11 | |
| 0.20.0 | 13 / 11 | |
| 0.19.0 | 13 / 11 | |
| 0.18.0 | 13 / 9 | |
| 0.17.0 | 13 / 9 | |
| 0.16.0 | 12 / 9 | |
| 0.15.0 | 12 / 9 | |
| 0.14.0 | 11 / 8 | |
| 0.13.0 | 11 / 8 | |
| 0.12.0 | 11 / 8 | |
| 0.11.0 | 11 / 8 | |
| 0.10.0 | 11 / 8 | |
| 0.6.0 | 9 / 8 | |
| 0.5.1 | 9 / 8 | |
| 0.5.0 | 9 / 8 | |
| 0.4.1 | 9 / 12 | |
| 0.4.0 | 9 / 12 | |
| 0.3.0 | 9 / 11 | |
| 0.2.2 | 9 / 11 | |
| 0.2.1 | 9 / 11 | |
| 0.2.0 | 9 / 11 | |
| 0.1.2 | 7 / 10 | |
| 0.1.1 | 7 / 10 | |
| 0.1.0 | 7 / 10 | |
| 0.0.1 | 0 / 0 |
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.