@satisfactory-dev/ajv-utilities
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): Package ships compiled TS output; file count growth reflects expanded module exports, not injected code. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size growth matches addition of compiled JS/DTS files for new modules; no obfuscation or suspicious payloads. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 0.27.3 | 0 / 6 | |
| 0.27.2 | 0 / 6 | |
| 0.27.1 | 0 / 6 | |
| 0.27.0 | 0 / 6 | |
| 0.26.0 | 0 / 6 | |
| 0.25.1 | 0 / 6 | |
| 0.25.0 | 0 / 6 | |
| 0.24.0 | 0 / 6 | |
| 0.23.0 | 0 / 6 | |
| 0.22.0 | 0 / 6 | |
| 0.21.0 | 0 / 6 | |
| 0.20.0 | 0 / 6 | |
| 0.19.0 | 0 / 6 | |
| 0.18.0 | 0 / 6 | |
| 0.17.1 | 0 / 5 | |
| 0.17.0 | 0 / 5 | |
| 0.16.0 | 0 / 5 | |
| 0.15.0 | 0 / 5 | |
| 0.14.0 | 0 / 5 | |
| 0.13.0 | 0 / 5 | |
| 0.12.0 | 0 / 5 | |
| 0.11.1 | 0 / 5 | |
| 0.11.0 | 0 / 5 | |
| 0.10.0 | 0 / 5 | |
| 0.9.0 | 0 / 5 | |
| 0.8.0 | 0 / 6 | |
| 0.7.0 | 0 / 6 | |
| 0.6.0 | 0 / 6 | |
| 0.5.0 | 0 / 6 | |
| 0.4.1 | 0 / 6 | |
| 0.4.0 | 0 / 6 | |
| 0.3.0 | 0 / 6 | |
| 0.2.2 | 1 / 6 | |
| 0.2.1 | 1 / 7 | |
| 0.2.0 | 1 / 7 | |
| 0.1.2 | 1 / 7 |
v0.27.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.1
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.1
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.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.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.1
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.1
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.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.