agentic-db
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@pgpm/totp | AI (phantom-deps): SQL module declares pgpm deps used via config, not JS imports; stable pattern. | ai | |
| phantom-deps | phantom-dep:@pgpm/uuid | AI (phantom-deps): SQL module declares pgpm deps used via config, not JS imports; stable pattern. | ai | |
| phantom-deps | phantom-dep:@pgpm/types | AI (phantom-deps): SQL module declares pgpm deps used via config, not JS imports; stable pattern. | ai | |
| phantom-deps | phantom-dep:@pgpm/utils | AI (phantom-deps): SQL module declares pgpm deps used via config, not JS imports; stable pattern. | ai | |
| phantom-deps | phantom-dep:@pgpm/base32 | AI (phantom-deps): SQL module declares pgpm deps used via config, not JS imports; stable pattern. | ai | |
| phantom-deps | phantom-dep:@pgpm/stamps | AI (phantom-deps): SQL module declares pgpm deps used via config, not JS imports; stable pattern. | ai | |
| phantom-deps | phantom-dep:@pgpm/inflection | AI (phantom-deps): SQL module declares pgpm deps used via config, not JS imports; stable pattern. | ai | |
| phantom-deps | phantom-dep:@pgpm/jwt-claims | AI (phantom-deps): SQL module declares pgpm deps used via config, not JS imports; stable pattern. | ai | |
| phantom-deps | phantom-dep:@pgpm/database-jobs | AI (phantom-deps): SQL module declares pgpm deps used via config, not JS imports; stable pattern. | ai | |
| phantom-deps | phantom-dep:@pgpm/metaschema-schema | AI (phantom-deps): SQL module declares pgpm deps used via config, not JS imports; stable pattern. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.5.0 | 11 / 5 | |
| 1.4.0 | 11 / 5 | |
| 1.2.1 | 11 / 5 | |
| 1.2.0 | 11 / 5 | |
| 1.1.1 | 11 / 5 | |
| 1.1.0 | 11 / 5 | |
| 1.0.0 | 11 / 5 | |
| 0.4.0 | 11 / 5 | |
| 0.3.2 | 11 / 5 | |
| 0.3.1 | 11 / 5 | |
| 0.3.0 | 10 / 5 | |
| 0.2.0 | 0 / 5 | |
| 0.0.2 | 0 / 2 |
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
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. Consider requesting the maintainer enable provenance via CI/CD.
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.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.