@getpara/graz-connector
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Publisher has 163 approved packages without provenance; stable pattern for this org. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; sparse metadata is expected for internal connector packages in the @getpara ecosystem. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across @getpara ecosystem packages; not a malicious indicator. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 2 / 9 | |
| 3.0.0 | 2 / 9 | |
| 2.32.1 | 2 / 9 | |
| 2.32.0 | 2 / 9 | |
| 2.31.0 | 2 / 9 | |
| 2.28.0 | 2 / 9 | |
| 2.27.0 | 2 / 9 | |
| 2.26.0 | 2 / 9 | |
| 2.25.0 | 2 / 9 | |
| 2.24.0 | 2 / 9 | |
| 2.22.0 | 2 / 9 | |
| 2.21.0 | 2 / 9 | |
| 2.20.0 | 2 / 9 | |
| 2.19.0 | 2 / 9 | |
| 2.18.0 | 2 / 9 | |
| 2.16.0 | 2 / 9 | |
| 2.15.0 | 2 / 9 | |
| 2.14.0 | 2 / 9 | |
| 2.13.0 | 2 / 9 | |
| 2.12.0 | 2 / 9 | |
| 2.11.0 | 2 / 9 | |
| 2.10.0 | 2 / 9 | |
| 2.6.0 | 2 / 9 | |
| 2.5.0 | 2 / 9 | |
| 2.3.0 | 2 / 9 | |
| 2.2.0 | 2 / 9 | |
| 2.1.0 | 2 / 9 | |
| 2.0.0 | 2 / 9 |
v3.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nsquare) than the most recent previously approved version (tbosch) on 2026-06-05, but nsquare is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tbosch) than the most recent previously approved version (nsquare) on 2026-05-28, but tbosch is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.32.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.