@tuturuuu/internal-api
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from manual publish to GitHub Actions CI with SLSA attestation; consistent with monorepo automation. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase matches expanded subpath exports and new infrastructure modules in the monorepo package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): 80 new files correspond to the many new subpath export entries added in this version. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; missing metadata is expected for org-internal tooling, not a spam/malware signal. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.22.0 | 2 / 4 | |
| 0.21.0 | 2 / 4 | |
| 0.20.0 | 2 / 4 | |
| 0.19.0 | 2 / 4 | |
| 0.18.0 | 2 / 4 | |
| 0.17.0 | 2 / 4 | |
| 0.15.0 | 2 / 4 | |
| 0.14.1 | 2 / 4 | |
| 0.14.0 | 2 / 4 | |
| 0.13.0 | 2 / 4 | |
| 0.12.0 | 2 / 4 | |
| 0.11.0 | 2 / 4 | |
| 0.10.0 | 2 / 4 | |
| 0.9.0 | 1 / 5 | |
| 0.8.0 | 1 / 5 | |
| 0.7.1 | 1 / 5 | |
| 0.7.0 | 1 / 5 | |
| 0.5.0 | 1 / 5 | |
| 0.4.1 | 1 / 5 | |
| 0.4.0 | 1 / 5 | |
| 0.3.0 | 1 / 5 | |
| 0.2.1 | 1 / 5 | |
| 0.2.0 | 1 / 4 | |
| 0.1.0 | 1 / 4 | |
| 0.0.2 | 1 / 4 | |
| 0.0.1 | 1 / 4 |
v0.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-25. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.