@things-factory/integration-base
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@operato/moment-timezone-es | AI (phantom-deps): Declared in dependencies and referenced in config; phantom-dep heuristic fires because it's not directly imported in JS. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in migrations/index.js is a standard pattern for loading migration files by path; not a security risk. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is used to decode AWS Lambda log results; legitimate AWS SDK usage pattern. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 9.2.13 | 18 / 0 | |
| 9.1.19 | 18 / 0 | |
| 8.0.64 | 18 / 0 | |
| 8.0.63 | 18 / 0 | |
| 6.4.10 | 17 / 1 | |
| 6.4.8 | 17 / 1 | |
| 4.3.791 | 17 / 0 | |
| 4.3.788 | 17 / 0 | |
| 4.3.776 | 17 / 0 | |
| 4.3.770 | 17 / 0 | |
| 4.3.767 | 17 / 0 | |
| 4.3.764 | 17 / 0 | |
| 4.3.755 | 17 / 0 | |
| 4.3.752 | 17 / 0 | |
| 4.3.743 | 17 / 0 | |
| 4.3.740 | 17 / 0 | |
| 4.3.738 | 17 / 0 | |
| 4.3.695 | 17 / 0 | |
| 4.3.689 | 17 / 0 | |
| 4.3.686 | 17 / 0 | |
| 4.3.685 | 17 / 0 | |
| 4.3.684 | 17 / 0 | |
| 4.3.682 | 17 / 0 | |
| 4.3.677 | 17 / 0 | |
| 4.3.675 | 17 / 0 | |
| 4.3.673 | 17 / 0 | |
| 4.3.672 | 17 / 0 | |
| 4.3.671 | 17 / 0 | |
| 4.3.653 | 17 / 0 | |
| 4.3.652 | 17 / 0 |
v9.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.791
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.788
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.776
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.770
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.767
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.764
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.755
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.752
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.743
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.740
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.738
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.695
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.689
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.686
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.685
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.684
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.682
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.677
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.675
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.673
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.672
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.671
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.653
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.652
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.