@introspection-sdk/introspection-proxy
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publisher has strong track record; missing gitHead reflects a publish environment change, not a malicious signal for this package. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 0.13.0 | 2 / 5 | |
| 0.12.0 | 2 / 5 | |
| 0.11.0 | 2 / 5 | |
| 0.10.0 | 2 / 5 | |
| 0.9.3 | 2 / 5 | |
| 0.9.2 | 2 / 5 | |
| 0.9.1 | 2 / 5 | |
| 0.9.0 | 2 / 5 | |
| 0.8.3 | 2 / 5 | |
| 0.8.2 | 2 / 5 | |
| 0.8.1 | 2 / 5 | |
| 0.8.0 | 2 / 5 | |
| 0.7.2 | 1 / 5 | |
| 0.7.1 | 1 / 5 | |
| 0.7.0 | 1 / 5 | |
| 0.6.5 | 1 / 5 | |
| 0.6.4 | 1 / 5 | |
| 0.6.3 | 1 / 5 | |
| 0.6.2 | 1 / 5 | |
| 0.6.1 | 1 / 5 | |
| 0.6.0 | 1 / 5 | |
| 0.5.9 | 1 / 5 | |
| 0.5.8 | 1 / 5 | |
| 0.5.7 | 1 / 5 | |
| 0.5.6 | 1 / 5 | |
| 0.5.5 | 1 / 5 | |
| 0.5.4 | 1 / 5 | |
| 0.5.3 | 1 / 5 | |
| 0.5.2 | 1 / 5 | |
| 0.5.1 | 1 / 5 | |
| 0.5.0 | 1 / 5 | |
| 0.4.10 | 1 / 5 | |
| 0.4.9 | 1 / 5 | |
| 0.4.8 | 1 / 5 | |
| 0.4.7 | 1 / 5 | |
| 0.4.5 | 1 / 5 | |
| 0.1.0 | 1 / 5 |
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.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: brightsparc.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: brightsparc.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: brightsparc.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: brightsparc.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: brightsparc.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.