@papit/information
Quite an abstract package to collect package information about other packages
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is confirmed by SLSA provenance attestation from the same org repo. | ai | |
| semgrep | semgrep:toplevel-fetch | AI (semgrep): Fires on minified bundle; visible code shows only fs/path imports — no actual fetch call evident. Consistent with bundled monorepo CLI tool. | ai | |
| phantom-deps | phantom-dep:@papit/terminal | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for bundled packages. | ai | |
| phantom-deps | phantom-dep:@papit/bundle-ts | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for bundled packages. | ai | |
| phantom-deps | phantom-dep:@papit/data-structure | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for bundled packages. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.0.6 | 5 / 2 | |
| 0.0.5 | 5 / 2 | |
| 0.0.4 | 5 / 2 | |
| 0.0.3 | 5 / 2 | |
| 0.0.2 | 5 / 2 | |
| 0.0.1 | 4 / 3 |
v0.0.6
2 findingsThis version was published by a different npm account than previous versions on 2026-05-14. 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.
v0.0.5
2 findingsThis version was published by a different npm account than previous versions on 2026-05-13. 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.
v0.0.4
2 findingsThis version was published by a different npm account than previous versions on 2026-04-30. 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.
v0.0.3
2 findingsThis version was published by a different npm account than previous versions on 2026-04-29. 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.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.